Post by Robert Gomezi Post by Victor Duchovni
It is normal, but the reason is simply that any restriction that involves
the sender address needs to resolve the sender address via trivial-rewrite
in order to obtain the standard form of the address. This process also
computes the address class and transport. It is not related to the
"reject_unlisted_recipient" restriction, which is only concerned with
the recipient address.
The restrictions that pertain to the sender address and trigger sender
So even with an empty smtpd_sender_restrictions (which is the
default), since smtpd_recipient_restrictions is valid within
smtpd_sender_restrictions and reject_unlisted_recipient defaults to
yes, this implies that sender address resolution always occur and if
virtual_alias_domains is looked via SQL/LDAP then the sender address
is looked up via the corresponding SQL query.
No, the sender is only resolved if restrictions that make use of the
sender address are configured (regardless of whether they are listed
in smtpd_sender_restrictions or smtpd_recipient_restrictions). The
URL documents which restrictions use the sender address, but they
can be used in other contexts (e.g. recipient or data restrictions).
The sender is also resolved if reject_unlisted_sender is on by default
(i.e. smtpd_reject_unlisted_sender = yes). For Postfix snapshots between:
Cleanup: the Postfix SMTP server rejects a MAIL FROM address
that matches a local, virtual or relay domain, while the
address is not listed in the corresponding local, virtual
or relay recipient table.
Feature: the reject_unlisted_sender(recipient) SMTPD access
restriction rejects an address that matches a local, virtual
or relay domain, while the address is not listed in the
corresponding local, virtual or relay recipient table.
Compatibility: smtpd_reject_unlisted_sender is turned off
by default, to avoid trouble with with in-house software
that sends out mail software with an unreplyable address.
senders are resolved by default and unlisted senders are always rejected.
Postfix 2.1.0 was released on 20040421, and does not by default resolve
Finally, in addition to the above discussion of sender resolution, if
mydestination is defined via an SQL or LDAP table, and canonical mappings
or From header rewrites are enabled, the sender domain will be checked
against the table in order to determine whether bare "user" keys should
be used in the rewrite lookup key.
Disclaimer: off-list followups get on-list replies or get ignored.
Please do not ignore the "Reply-To" header.
To unsubscribe from the postfix-users list, visit
http://www.postfix.org/lists.html or click the link below:
If my response solves your problem, the best way to thank me is to not
send an "it worked, thanks" follow-up. If you must respond, please put
"It worked, thanks" in the "Subject" so I can delete these quickly.