Re: smtpd_recipient_restrictions -- Best Practices

2011-12-08 Thread Noel Jones
On 12/8/2011 1:17 PM, Peter L. Berghold wrote: > smtpd_recipient_restrictions = > permit_mynetworks, OK. > permit_auth_destination, Permits all mail handled by your server. > reject_unauth_destination, Rejects all mail not handled by your server. Nothing left after that... N

Re: smtpd_recipient_restrictions -- Best Practices

2011-12-08 Thread /dev/rob0
Where did you find this list? There are major issues here. On Thursday 08 December 2011 13:17:44 Peter L. Berghold wrote: > smtpd_recipient_restrictions = > permit_mynetworks, fine ... > permit_auth_destination, "If the destination is served by this host, accept the mail." > r

Re: smtpd_recipient_restrictions -- Best Practices

2011-12-08 Thread Brian Evans - Postfix List
On 12/8/2011 2:17 PM, Peter L. Berghold wrote: > smtpd_recipient_restrictions = > permit_mynetworks, > permit_auth_destination, This restriction at this location will IGNORE all RBL lookups when mail is destined for your system. I suggest removing it as it is implied if reject_unauth_de

Re: smtpd_recipient_restrictions -- Best Practices

2011-12-08 Thread Duane Hill
On Thursday, December 08, 2011 at 19:17:44 UTC, pe...@berghold.net confabulated: > smtpd_recipient_restrictions = > permit_mynetworks, > permit_auth_destination, > reject_unauth_destination, > check_sender_access hash:/etc/postfix/access, > permit_sasl_authenticated, >

Re: smtpd_recipient_restrictions -- Best Practices

2011-12-08 Thread Peter L. Berghold
smtpd_recipient_restrictions = permit_mynetworks, permit_auth_destination, reject_unauth_destination, check_sender_access hash:/etc/postfix/access, permit_sasl_authenticated, reject_unauth_pipelining, reject_non_fqdn_sender, reject_non_fqdn_recipient, reject_

Re: smtpd_recipient_restrictions -- Best Practices

2011-12-08 Thread /dev/rob0
On Thursday 08 December 2011 13:04:13 Peter L. Berghold wrote: > Is there are "best practice" concerning the ordering of the > directives to the right hand side of the "=" for > smtpd_recipient_restrictions? Consider the relative costs of the restrictions. For example, a hash: table access(5) loo

Re: smtpd_recipient_restrictions -- Best Practices

2011-12-08 Thread Matt Hayes
On 12/8/2011 2:04 PM, Peter L. Berghold wrote: Hi folks, Hope this isn't too dumb a question, but here goes: Is there are "best practice" concerning the ordering of the directives to the right hand side of the "=" for smtpd_recipient_restrictions? The reason I'm asking is I added a set of line

smtpd_recipient_restrictions -- Best Practices

2011-12-08 Thread Peter L. Berghold
Hi folks, Hope this isn't too dumb a question, but here goes: Is there are "best practice" concerning the ordering of the directives to the right hand side of the "=" for smtpd_recipient_restrictions? The reason I'm asking is I added a set of lines for RBL reverse DNS and they don't seem to