OSEC

Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com
 
Re: [postfix 2.1.5] Problem using check_recipient_access with smtpd_client_restrictions

From: Noel Jones (njonesmegan.vbhcs.org)
Date: Thu Dec 16 2004 - 16:07:43 CST


At 03:50 PM 12/16/2004, Charles Quesenberry wrote:
>Eric Fung wrote:
>
>>
>>Only change I made was to add the check_recipient_access to
>>smtpd_client_restrictions
>>I'm putting only that config line in for now, I don't need the rest of
>>my config out for the world to see =P
>>
>>Working Line:
>>smtpd_client_restrictions = permit_mynetworks,
>>permit_sasl_authenticated, check_client_access
>>hash:/etc/postfix/client-access, reject_rbl_client t1.dnsbl.net.au,
>>permit
>>
>>Broken Line:
>>smtpd_client_restrictions = permit_mynetworks,
>>permit_sasl_authenticated, check_client_access
>>hash:/etc/postfix/client-access, check_recipient_access
>>hash:/etc/postfix/dnsbl_whitelist, reject_rbl_client t1.dnsbl.net.au,
>>permit
>>
>>
>
>Looking at the documentation, I don't see a "check_recipient_access" as an
>available smtpd_client_restriction.
>http://www.postfix.org/postconf.5.html#smtpd_client_restrictions
>
>Try moving that restriction to smtpd_recipient_restrictions. But take
>heed of the IMPORTANT notice -
>http://www.postfix.org/postconf.5.html#smtpd_recipient_restrictions
>

If you read a little further, you will see "Other restrictions that are
valid in this context:" which explains that you CAN use
check_recipient_access maps under smtpd_client_restrictions as long as the
default smtpd_delay_reject=yes is set.

The OP's problem is explained in his log files.

--
Noel Jones