07.05.22, 21:18 +0200, Wietse Venema:

James Feeney:
At http://www.postfix.org/postconf.5.html :

----
smtpd_reject_unlisted_recipient (default: yes)

Request that the Postfix SMTP server rejects mail for unknown
recipient addresses, even when no explicit reject_unlisted_recipient
access restriction is specified. This prevents the Postfix queue
from filling up with undeliverable MAILER-DAEMON messages.

An address is always considered "known" when it matches a virtual(5) alias or a 
canonical(5) mapping.

If that last sentence above is confusing, then I can invert the
text to make it consistent with its context.

     (no change) Request that the Postfix SMTP server rejects mail
     for unknown recipient addresses, even when no explicit
     reject_unlisted_recipient access restriction is specified. This
     prevents the Postfix queue from filling up with undeliverable
     MAILER-DAEMON messages.

     (inverted) The recipient address is unknown when it does not
     match a virtual(5) alias or a canonical(5) table, plus one of
     the following conditions holds:

*The recipient domain matches $mydestination, $inet_interfaces or 
$proxy_interfaces, but the recipient is not listed in $local_recipient_maps, 
and $local_recipient_maps is not null.
*The recipient domain matches $virtual_alias_domains but the recipient is not 
listed in $virtual_alias_maps.
*The recipient domain matches $virtual_mailbox_domains but the recipient is not 
listed in $virtual_mailbox_maps, and $virtual_mailbox_maps is not null.
*The recipient domain matches $relay_domains but the recipient is not listed in 
$relay_recipient_maps, and $relay_recipient_maps is not null.

Just my 2 cents: although this inversion is - of course - logically correct, for me it undoes the effect of clarification that comes with explicitly stating that all canonical or virtual mappings are considered known.
I'd even propose to simply *add* the sentence
'An address is considered "known" when [...]'
after the list of conditions. Even though that technically means that the same information is given twice, it would make it much easier for me to grasp the meaning of the whole documentation item.

--
Regards
  mks

Reply via email to