I’ve spent more time reviewing and while my observations may be flawed, they do
seem to be consistent. What I continue to observe is that when an address is
matched in /etc/alias, that the smtp_recipient_restrictions are not processed
and therefore the suggested restrictions are not having any
On 21 Dec 2017, at 18:06 (-0500), Doe wrote:
In the case of a server that receives mail for a domain and also
allows clients to send mail through it (via AUTH’d clients), does
smtpd_recipent_restrictions apply to recipients at the domain or to
recipients of mail sent by the AUTH’d clients or b
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:
> , 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-
in Postfix 3.3, and will be in the stable
release in a month or so.
Wietse
20171223
Feature: Milters can now send RET and ENVID arguments in
SMFIR_CHGFROM requests.
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_recipien
