Guy wrote: > 2009/3/31 Nigel Kukard <[email protected]>: > >> This would happen if you are permitting traffic before the first policyd >> check in RCPT stage. Please paste your postfix restrictions. >> > > smtpd_recipient_restrictions = > reject_non_fqdn_sender, > reject_unknown_sender_domain, > reject_unknown_recipient_domain, > permit_mynetworks, > permit_sasl_authenticated, > reject_unauth_destination, > check_client_access cidr:/etc/postfix/postfix-dnswl-permit, > check_client_access cidr:/etc/postfix/postfix-dnswl-custom, > reject_invalid_hostname, > reject_rbl_client zen.spamhaus.org, > reject_rbl_client bl.spamcop.net, > reject_rbl_client b.barracudacentral.org, > reject_rbl_client psbl.surriel.com, > reject_rhsbl_client zen.spamhaus.org, > reject_rhsbl_client bl.spamcop.net, > check_policy_service inet:127.0.0.1:10031, > permit > > smtpd_end_of_data_restrictions = > check_policy_service inet:127.0.0.1:10031 > > > Exactly, you are permitting traffic before policyd gets a request, so it is not going to know about the messages and its not going to record any session data.
-N
smime.p7s
Description: S/MIME Cryptographic Signature
_______________________________________________ Users mailing list [email protected] http://lists.policyd.org/mailman/listinfo/users
