Hi Wietse, The noted difference is for b...@trashcan.org, smtpd_recipient_restrictions is never evaluated at all. For b...@trashcan.org there is no ‘START Recipient address RESTRICTIONS’ or any of the related logs for smtpd_recipient_restrictions. For arling...@trashcan.org, smtp_recipient_restrictions is processing properly as is noted in the log excerpt.
The same behavior of smtpd_recipient_restrictions not processing occurs for any address that appears in /etc/aliases. I’m happy to include more logs, but the key difference in behavior is as noted. My question is: is this expected behavior? Is it expected that addresses which appear in /etc/aliases for the mydestination domain bypass smtpd_recipient_restrictions? Thanks, Justin > On Dec 23, 2017, at 5:22 PM, Wietse Venema <wie...@porcupine.org> wrote: > > > Here is the start of evaluating smtpd_recipient_restrictions: > >> Dec 23 16:06:34 ip-172-31-54-95 postfix/smtpd[13472]: extract_addr: in: >> <arling...@trashcan.org>, result: arling...@trashcan.org >> Dec 23 16:06:34 ip-172-31-54-95 postfix/smtpd[13472]: >>> START Recipient >> address RESTRICTIONS <<< >> Dec 23 16:06:34 ip-172-31-54-95 postfix/smtpd[13472]: generic_checks: >> name=permit_mynetworks >> Dec 23 16:06:34 ip-172-31-54-95 postfix/smtpd[13472]: permit_mynetworks: >> mail-qt0-f171.google.com 209 >> >> With b...@trashcan.org at the same point > > You forgot to include the remaining postfix/smtpd[13472]: > records, including the record that marks the end of evaluating > smtpd_recipient_restrictions: > >>>> END Recipient address RESTRICTIONS <<< > > You forgot to include the smtpd logging for b...@trashcan.org, to > demonstrate the difference, if any. > > Wietse
