On Thu, Dec 10, 2009 at 08:03:01PM +0100, Simon Klempert wrote:
> >> Dec 10 18:37:07 zimbra postfix/smtp[542]: 81058E3232:
> >> to=<bou...@aruba.com>, orig_to=<bounce+0.6...@xxxxxxxx.com>,
> >> relay=127.0.0.1[127.0.0.1]:10024, delay=14, delays=8.8/0/0.01/4.8,
> >> dsn=2.0.0, status=sent (250 2.0.0 Ok, id=00532-01, from
> >> MTA([127.0.0.1]:10025): 250 2.0.0 Ok: queued as B4921E3233)
> >
> > This did get rewritten. Your configuration discards the address extension
> > after virtual (or perhaps canonical or both) rewriting.
>
> OK, do you have a clue how to disable this rewriting?
Disabling of rewriting before the filter is described in FILTER_README.html
> propagate_unmatched_extensions = canonical
This is a reasonable setting when the final mailstore does not understand
address extensions. I use it also, when forwarding mail to MSFT Exchange,
for example. This is why the extension is dropped, but the solution is
most probably to delay address rewriting, rather than enable extension
propagation, which can cause non-delivery downstream.
--
Viktor.
Disclaimer: off-list followups get on-list replies or get ignored.
Please do not ignore the "Reply-To" header.
To unsubscribe from the postfix-users list, visit
http://www.postfix.org/lists.html or click the link below:
<mailto:majord...@postfix.org?body=unsubscribe%20postfix-users>
If my response solves your problem, the best way to thank me is to not
send an "it worked, thanks" follow-up. If you must respond, please put
"It worked, thanks" in the "Subject" so I can delete these quickly.
