On Mon, Dec 30, 2019 at 04:37:32PM +1300, Peter wrote:
> If someone uses virtual_address_domains and has
> "receive_override_options = no_address_mappings", then postfix will
> kick back an error of "User unknown in virtual alias table" for any
> recipient in that domain.
Addresses in virtual_alias_domains resolve to the error transport,
unless rewritten to a "real domain", typically via virtual_alias_maps.
But, content_filter bypasses transport resolution, since all recipients
go to the filter transport, so the below is not what typically happens.
> User has a content filter configured which re-injects to postfix on
> another port which does not have no_address_mappings set. The intent
> here is for address mappings to be ignored and the content filter run
> initially then upon re-injection for the address mappings to be
> processed and the message routed as appropriate.
How is the content filter specified? Is this a multi-instance
configuration with "default_transport" set to the filter, or a single
instance configuration with "-o content_filter=" in the pre-filter
master.cf SMTP listener?
> Because no_address_mappings is set and the recipient address is in the
> virtual alias address class, however, the message instead gets
> rejected initially with the above mentioned error.
That is not what happens when "content_filter" is specified.
> Is this behavior intentional or just a side effect of how
> no_address_mappings is implemented?
http://www.postfix.org/DEBUG_README.html#mail
Post:
* postconf -nf
* postconf -Mf
* logs showing all processing of a rejected message
--
Viktor.
