[pfx] Re: Duplicate deliveries of expanded addresses (Was: Re: Avoiding message doubling via virtual aliases)
Wietse Venema via Postfix-users <[email protected]> Sat, 16 May 2026 18:34:58 -0400 (EDT)
| Newsgroups | gmane.mail.postfix.user |
|---|---|
| Message-ID | <[email protected]> |
Wietse Venema via Postfix-users: > Steffen Nurpmeso via Postfix-users: > > Wietse Venema via Postfix-users wrote in > > <[email protected]>: > > ... > > |That is insufficient data to reproduce the observation. > > > > As an idiot, i tried this again, locally. > > > > mydestination = kent, $myhostname, lists.kent, $myhostname.$mydomain localhost.$mydomain, localhost > > > > virtual_alias_maps = lmdb:$meta_directory/virtual, > > regexp:$meta_directory/virtual_re > > > > In "aliases" > > > > vietse: steffen Sorry,. I missed that. > > In "virtual_re" > > > > /^(knodel(.*))@kent/ ${1}@lists.kent > > /^knodel@lists\.kent$/ vietse > > > > Then > > > > /usr/sbin/sendmail -bv [email protected] knodel@kent > > > > gives > > > > May 16 17:15:17 kent postfix/pickup[24980]: 80E95219BDF: uid=1000 from=<steffen> > > May 16 17:15:17 kent postfix/cleanup[24990]: 80E95219BDF: message-id=<[email protected]> > > May 16 17:15:17 kent postfix/qmgr[24981]: 80E95219BDF: from=<[email protected]>, size=304, nrcpt=2 (queue active) > > > > ^ nrcpt=2 > > You did not report the envelope recipients as requested (place the > message on hold, innspect with postcat, then release from hold > and trigger delivery "with postqueue -f".) > > According to the config above, one would expect: > > [email protected] -> vietse -> vietse@myorigin > knodel@kent -> [email protected] These recipients resolve to a domain in mydestination (local delivery agent). Because the recipients resolve to domain in mydestination, they will be delivered in parallel. Each recipient is passed to a DIFFERENT local delivery agent process. in the logging below, one local delivery agent has process ID 24992, the other 24993. > > May 16 17:15:17 kent postfix/local[24992]: 80E95219BDF: to=<[email protected]>, orig_to=<[email protected]>, relay=local, delay=0.07, delays=0.06/0/0/0, dsn=2.0.0, status=deliverable (delivers to mailbox) > > May 16 17:15:17 kent postfix/local[24993]: 80E95219BDF: to=<[email protected]>, orig_to=<knodel@kent>, relay=local, delay=0.07, delays=0.06/0.01/0/0, dsn=2.0.0, status=deliverable (delivers to mailbox) The existing Postfix architecture cannot deduplicate that. It would have to compute the delivery graph ahead of time, including virtual and local aliasing and forwarding. That graph would have to be available in one place, so that an all-seeing kremlin scheduler can detect ahead of time that some combination of aliasing mechanisms will resolve different addresses to the same mailbox. Wietse _______________________________________________ Postfix-users mailing list -- [email protected] To unsubscribe send an email to [email protected]