Mathias Jeschke:
> Thanks Wietse and Viktor!
>
> On 2015-04-17 at 02:39 Wietse Venema wrote:
>
> > The solution for you would be that:
> >
> > 1) Postfix always records the original recipient, regardless of the
> > enable_original_recipient setting, so that address verification
> > works.
> >
> > 2) The enable_original_recipient parameter determines whether the
> > original address will be used for address deduplication and
> > whether it will show up in X-Original-To: headers, maillog
> > records, and so on. This requires that a bunch of tests be
> > replaced by with other tests. We can even introduce finer-grained
> > control (enable_original_recipient = x-original-to, deduplication,
> > logging, ...).
>
> I would love to see this solution in an upcoming postfix release as it
> would simplify my setup and help to make it more robust.
It's on the wishlist. Meanwhile I'm drinking from a firehose
at my new job, so development cycles are limited.
> Meanwhile, I have successfully tested two workarounds:
>
[postmulti]
> None of the above has a concept to share common parts of the
> main.cf among the instances and updating the actual main.cf at
> (re-)starts/reloads.
postmulti has an iterator mode that allows you to apply the same
command to multiple instances.
To update multiple main.cf (or master.cf) files:
# postmulti -x postconf xxx=yyy
# postmulti -x postconf -M xxx=yyy
This is in addition to "postmulti -p" which is dedicated to
"postfix" commands.
Wietse
