This seemed initially promising, but one of our primary internal mail systems won't validate the +/=-style address extension, and with the Return-path/envelope-sender encoded as <host-tag>+<user>=<valid address>@<valid domain>, any bounces just die with recipient unknown.
(postfix 2.3.3 is unfortunately the most recent version provided in Red Hat's enterprise repository. I could update it, of course, but we try to stick with core packages where possible). On Fri, May 2, 2014 at 11:30 PM, Viktor Dukhovni <postfix-us...@dukhovni.org > wrote: > On Fri, May 02, 2014 at 10:15:45PM -0500, /dev/rob0 wrote: > > On Fri, May 02, 2014 at 05:26:02PM -0400, > > Jonathan Engbrecht wrote: > > > postfix 2.3.3 > > > > Note that Viktor's suggestion of multiple instances assumes a > > slightly less ancient Postfix version; postmulti(1) began with > > Postfix 2.6. Time to upgrade? > > I was not suggesting multiple instances, merely the rewriting > methodology of the nullclient configuration described in the > document. This said Postfix 2.3 is rather old, and if the OP gets > a chance, running something more recent (2.9 or later) is not a > bad idea. > > -- > Viktor. >
