On Thu, May 09, 2019 at 07:13:22PM +0200, Andreas Thienemann wrote: > I was under the impression, that smtpd_recipient_restrictions and other > restriction configuration items were being processed top to bottom.
Show logs. Show complete config. See http://www.postfix.org/DEBUG_README.html#mail. As this is not your first question on this list, I assume you have been told about that already. > smtpd_recipient_restrictions = check_recipient_access > proxy:mysql:/etc/postfix/bounce_spam_alias.cf > check_recipient_access > proxy:mysql:/etc/postfix/bounce_routes.cf > reject_unknown_recipient_domain > reject_unverified_recipient > reject_unlisted_recipient > So I am unclear why this is happening. I have a smtpd_sender_restrictions > entry that seems to work top-to-bottom. > > smtpd_sender_restrictions = check_client_access inline:{10.1.1.1=OK} > reject_unknown_sender_domain Don't split restrictions into multiple lists. > May 9 18:47:30 mailin01 postfix/smtpd[24094]: >>> START Recipient address > RESTRICTIONS <<< _Don't_ enable verbose logging unless instructed to. > May 9 18:47:30 mailin01 postfix/smtpd[24094]: generic_checks: > name=reject_unauth_destination I don't see reject_unauth_destination in anything you showed. I'm currently not sure if it can be use implicit, but I don't think so. > Does anyone have any pointers what I might be missing? You don't want to use recipient verification, make sure you can live without. Drop mysql until you know how it works. Bastian -- Women professionals do tend to over-compensate. -- Dr. Elizabeth Dehaver, "Where No Man Has Gone Before", stardate 1312.9.
