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,
ket:
wanted attribute: request
I’ll re-ask, are addresses listed in /etc/aliases expected to bypass
smtp_recipient_restrictions?
If so, I’ll give up on this particular approach. If not, I’ll keep trying to
debug.
Thanks,
Justin
> On Dec 14, 2017, at 6:58 AM, Wietse Venema <wie.
017, at 06:58, Wietse Venema <wie...@porcupine.org> wrote:
>
> Justin Peavey:
>>
>> Thanks for the reply, unfortunately the approach doesn?t seem to work for
>> me. It appears that that the regardless of the smtp_recipient_restrictions
>> setting, that any add
Thanks for the reply, unfortunately the approach doesn’t seem to work for me.
It appears that that the regardless of the smtp_recipient_restrictions setting,
that any addresses listed in /etc/aliases addressed to $mydomain is bypassing
any blocking/filtering. Is this expected behavior?
>