Raimar Sandner:
> Hi,
>
> there seems to be a regression after upgrading from postfix 3.1.4 to 3.2.2 on
> arch linux. I'm using virtual aliases with
>
> recipient_delimiter = .
> propagate_unmatched_extensions = canonical, virtual
>
> For a given virtual mapping
>
> [email protected] => [email protected]
>
> postfix 3.1 will map [email protected] to [email protected]. This is
> working perfectly fine: When I receive a mail on [email protected],
> postfix 3.1 logs
>
> ------ snip -------
> postfix/lmtp[16546]: 4FCAF44764: to=<[email protected]>,
> orig_to=<[email protected]>, relay=<hostname
> removed>[private/dovecot-lmtp], delay=1.2, delays=0.1/0.01/0.01/1.1,
> dsn=2.0.0, status=sent (250 2.0.0 <[email protected]>
> Jw8BGpV3SVmjQAAAT7qhFg Saved)
> ------ snip -------
>
> This setup stopped working with postfix 3.2 with the exact same
> configuration. The extension is not propagated anymore, postfix 3.2 logs
>
> ------ snip -------
> postfix/lmtp[17650]: B4E614030E: to=<[email protected]>,
> orig_to=<[email protected]>, relay=<hostname
> removed>[private/dovecot-lmtp], delay=0.89, delays=0.07/0.01/0.01/0.8,
> dsn=2.0.0, status=sent (250 2.0.0 <[email protected]> bsYAMch/SVnzRAAAT7qhFg
> Saved)
> ------ snip -------
>
> How can I restore the behaviour of postfix 3.1? Your help is greatly
> appreciated! I'm glad to provide more information in case I forgot something
> relevant.
>
That will require a bugfix. After many years, the address mapping
code needed to be cleaned up, and I thought that all the tests would
have caught any incompatibilities, but apparently not.
Wietse
