|
Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com |
Re: 2.2.8 + amavisd + postgrey
From: Bill Bradford (mrbill
mrbill.net)
Date: Mon Feb 06 2006 - 10:27:31 CST
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Mon, Feb 06, 2006 at 07:59:25AM +0100, Ralf Hildebrandt wrote:
> Useless. Leave smtpd_helo_restrictions empty.
Done.
> > smtpd_sender_restrictions =
> > permit_mynetworks
> > reject_unauth_pipelining
> > reject_unknown_sender_domain
> > smtpd_recipient_restrictions =
> > permit_mynetworks
> > permit_mx_backup
> > permit_auth_destination
> > reject_unauth_destination
> > reject_unknown_recipient_domain
> > check_policy_service inet:127.0.0.1:6000
> > check_helo_access dbm:/etc/postfix/helo_checks
> Why didn't you put these into smtpd_helo_restrictions?
Because I thought where I put them is where they're *supposed* to go...
So I should move check_helo_access and the check_policy_service to
smtpd_helo_restrictions? Everything I've seen documentation-wise says
to put the policy service check under smtpd_recipient_restrictions.
Here's what I'm down to now:
smtpd_helo_restrictions =
smtpd_client_restrictions =
permit_mynetworks
reject_rbl_client sbl-xbl.spamhaus.org
smtpd_sender_restrictions =
smtpd_recipient_restrictions =
permit_mynetworks
permit_mx_backup
reject_unauth_destination
reject_unknown_sender_domain
check_helo_access dbm:/etc/postfix/helo_checks
check_policy_service inet:127.0.0.1:6000
smtpd_data_restrictions =
reject_unauth_pipelining
I tried moving the reject_rbl_client into the smtpd_recipient_restrictions
but it seemed to stop working when I did so.
Bill
--
Bill Bradford
Houston, Texas
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]