Thank you for the response. I do have a submission setup but you reminded me to look in he master.conf and disable rate limiting:
submission inet n - n - - smtpd -o syslog_name=postfix/submission -o smtpd_tls_security_level=encrypt -o smtpd_sasl_auth_enable=yes -o smtpd_reject_unlisted_recipient=no -o smtpd_recipient_restrictions= -o smtpd_relay_restrictions=permit_sasl_authenticated,reject -o smtpd_client_connection_count_limit=0 -o smtpd_client_connection_rate_limit=0 -o smtpd_client_recipient_rate_limit=0 -o smtpd_client_message_rate_limit=0 -o smtpd_client_new_tls_session_rate_limit=0 Are the *_limit=0 lines above correct for overriding the main.cf values? Thanks, Dave On Thu, Aug 4, 2016 at 3:50 PM, /dev/rob0 <r...@gmx.co.uk> wrote: > On Thu, Aug 04, 2016 at 02:25:19PM -0500, Dave Jones wrote: >> Is there something like permit_sasl_authenticated that >> could be put in the postscreen_access_list and the >> smtpd_client_event_limit_exceptions that could bypass >> dnsbl and rate limiting for SASL authenticated senders? > > No, since the SASL AUTH won't happen until the client is talking to > smtpd. > > You really do not want to put MUAs through postscreen. It is not > made for such a task. What you need to do is one of these choices: > 1. Have users use submission (port 587) > 2. Have a separate IP address (smtpd only) for submission on 25 > 3. Disable postscreen > -- > http://rob0.nodns4.us/ > Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
