On 27/04/2014 13:21, Wietse Venema wrote:
Matt Holgate:
Is there any way of avoiding this? I see there is a
'propagate_unmatched_extensions' parameter, but I'd have thought this
would have no effect as there is no extension in the original address.
No that is backwards. It propagates the extension that exists in the
original address and that is not matched by the lookup table.
original: name+...@example.com
table: n...@example.com -> foo...@example.net
result: foobar+...@example.net
Indeed - sorry, I didn't explain myself very well!
What I'm trying to achieve is to forward unextended addresses in my
parent's domain to extended addresses at Gmail.
My parents share a common gmail account, and use Gmail filters to sort
'private' messages sent to their address extensions into separate folders.
I've set this up on my Postfix server as follows:
dougandmari...@theirdomain.com holga...@gmail.com
d...@theirdomain.com holgates+d...@gmail.com
mari...@theirdomain.com holgates+mari...@gmail.com
The problem I am seeing is that when I send a message to e.g.
d...@theirdomain.com, it is getting mapped to holga...@gmail.com, i.e.
the destination address extension +doug is getting stripped out by Postfix.
I just wondered if there was any way to prevent this happening?
Many thanks
Matt.
