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: Eric Fung (efungshgmail.com)
Date: Mon Dec 20 2004 - 16:28:31 CST


On Mon, 20 Dec 2004 11:55:09 +1100, Eric Fung <efungshgmail.com> wrote:
> > What I should have said is,
> > Try moving *BOTH* your -
> > check_recipient_access hash:/etc/postfix/dnsbl_whitelist
> > and
> > reject_rbl_client t1.dnsbl.net.au
> > to smtpd_recipient_restrictions.
>
> Alright, tried with following changes.
>
> smtpd_client_restrictions = permit_mynetworks,
> permit_sasl_authenticated, check_client_access
> hash:/etc/postfix/client-access, permit
>
> smtpd_recipient_restrictions = reject_non_fqdn_recipient,
> reject_unknown_recipient_domain, check_recipient_access
> hash:/etc/postfix/dnsbl_whitelist, reject_rbl_client t1.dnsbl.net.au,
> permit_mynetworks, permit_sasl_authenticated,
> reject_unauth_destination, reject_multi_recipient_bounce, permit
>
> Still no go. Same problem, no welcome banner, logs report lost after CONNECT.
>
> Further, after I revert back to the old configuration, I have to bring
> down postfix with a stop and start before it starts working again. A
> reload still results in the daemon not responding to SMTP connections
> after the offending set of rules is loaded.
>
> A little wierd, no? =)
>
> Eric
>

No one has any suggestions to what could be causing this problem???
Or should I try to isolate it and file a bug report?

I'm sure someone out there would be running this sort of setup where a
domain on a virtual mailbox does not want to be included in the DNSBL
checking . . .

Eric