On 21/08/2013 15:49, P.V.Anthony wrote:
On 14/07/2013 06:08, Nigel Kukard wrote:On 07/12/2013 02:34 AM, P.V.Anthony wrote:Hi,Currently using policyd version 2.0.12 on centos 6 64bit with postfix. Activated the SPF module with add-header and not to reject. In the logs it is showing action=add-header but in the email source there do not seem to have the header added. Is anyone also using SPF module with add-header function? P.V.AnthonyIs there any other verdicts taking place? remember the postfix policy delegation protocol can only return 1 verdictFor incoming email, SPF and Greylisting are active. In the logs it does show that CheckSPF is done first then Greylisting. Could that be the reason? Here is an example.Aug 21 23:42:39 servername cbpolicyd[17030]: module=CheckSPF, action=add_header, host=202.40.249.76, helo=cp-prod-avas-8.fuse.kc2.sg.local, [email protected], [email protected], reason=spf_softfailAug 21 23:42:39 servername cbpolicyd[17030]: module=Greylisting, action=pass, host=202.40.249.76, helo=cp-prod-avas-8.fuse.kc2.sg.local, [email protected], to=user@example, reason=auto-whitelistedIs there some other setting I need to do so that the SPF headers can be seen?
Postfix only supports 1 verdict, add_header could possibly be overriden by "pass" although I'm very sure I added code to make add_header remain...
Try shove policyd in full debugging mode for protocols too and see what its sending back.
-N
smime.p7s
Description: S/MIME Cryptographic Signature
_______________________________________________ Users mailing list [email protected] http://lists.policyd.org/mailman/listinfo/users_lists.policyd.org
