On Mon, Feb 01, 2021 at 03:43:55PM +0100, Gerben Wierda wrote:
> > Yes, at the cost of a dedicated transport whose master.cf entry contains
> > an override for smtp_generic_maps:
> >
> > master.cf:
> > mycanon unix ... smtp
> > -o smtp_generic_maps=$mycanon_generic_maps
> >
> > main.cf:
> > transport_maps = inline:{ {example.com = mycanon:} }
> > mycanon_generic_maps = inline:{ { @$myorigin = [email protected]
> > } }
>
> Sorry for my dimness (not doing this daily) but do I understand this
> correctly as:
>
> - Message is deliverd to normal transport (smtp process A) first
No, absent prior content_filters that apply to all messages regardless
of recipient domain there's only one delivery, via the transport
specified in transport_maps.
Perhaps you're confusing incoming messages via smtpd(8) with
a delivery transport. The Postfix concept of transport is
an output-only concept. The smtpd(8) service is incoming mail.
> - transport_maps in main.cf says: “when recipient is example.com
> <http://example.com/>, use transport mycanon)
That's the one and only transport.
> - Message is delived to mycanon transport (smtp process B) from normal
> transport (smtp process A)
No, the queue manager routes the message directly to the
correct transport for each batch of recipients sharing
the same nexthop destination.
> - mycanon transport replaces myorigin with the alias
Correct.
--
Viktor.
