Re: rejections after limiting access to smtp auth

2019-12-11 Thread Matus UHLAR - fantomas
lists skrev den 2019-12-12 03:08: Seriously is there ever a case not to use port 587? On 12.12.19 08:29, Benny Pedersen wrote: depends on content filtering, if all clients is local all can use port 25 even in this case separation of submission port can help much. I prefer postscreen and

Re: rejections after limiting access to smtp auth

2019-12-11 Thread Benny Pedersen
lists skrev den 2019-12-12 03:08: Seriously is there ever a case not to use port 587? depends on content filtering, if all clients is local all can use port 25

Re: rejections after limiting access to smtp auth

2019-12-11 Thread Benny Pedersen
Jason R Cowart skrev den 2019-12-12 01:10: smtpd_recipient_restrictions = check_client_access cidr:/etc/postfix/access/restricted-local-only.cidr, check_recipient_access hash:/etc/postfix/access/recipient, Any thoughts? Thanks in advance. make check_resipient_access reused in

Re: rejections after limiting access to smtp auth

2019-12-11 Thread lists
Seriously is there ever a case not to use port 587?

Re: rejections after limiting access to smtp auth

2019-12-11 Thread Viktor Dukhovni
On Thu, Dec 12, 2019 at 12:10:07AM +, Jason R Cowart wrote: > We're moving to a configuration that will leverage the check_sasl_access > option to allow only those granted access to authenticate from outside the > local network and relay mail. Your submission users should be using port 587,

rejections after limiting access to smtp auth

2019-12-11 Thread Jason R Cowart
We're moving to a configuration that will leverage the check_sasl_access option to allow only those granted access to authenticate from outside the local network and relay mail. This are mostly working (at least amongst the list of users allowed to send--we'll evaluate the types of things