On 2/23/2012 10:28 AM, rg86...@airpost.net wrote: > Hello everyone, > > On 02/23/2012 05:57 AM, Noel Jones wrote: >> You can use an access map in the reinjection listener: >> >> # master.cf >> 127.0.0.1:10026 inet n - n - - smtpd >> ... >> -o >> smtpd_sender_restrictions=check_recipient_access,hash:/etc/postfix/spamtrap > > I moved the "check_recipient_access ..." to the reinjection listener on > 127.0.0.1:10026, receiving from the SPAMPD proxy filter on > 127.0.0.1:10025. > > I tried it in both > > smtpd_sender_restrictions=
Yes, that's where it goes unless you've (unwisely) set smtpd_delay_reject=no. > > and > > smtpd_recipient_restrictions= That works too, but needs additional settings. Simpler to put it in smtpd_sender_restrictions. > > which seems to make a bit more sense to my read. > > Still no luck - the spamtrap check is never triggered. For reporting a problem, please see: http://www.postfix.org/DEBUG_README.html#mail > On 02/23/2012 06:53 AM, /dev/rob0 wrote: >> I see the goal as being, in part, to detect a spammer in THIS >> transaction. That sounds reasonable to me. But the proper thing here >> would be to use a policy service in smtpd_data_restrictions. Recipient checks in smtpd_data_restrictions are ineffective with multi-recipient mail. When there are multiple recipients, check_recipient_access cannot be performed and is silently skipped, and policy services are supplied an empty recipient value. http://www.postfix.org/postconf.5.html#smtpd_data_restrictions As a general rule, avoid doing recipient checks in smtpd_data_restrictions. -- Noel Jones
