On Sep 25, 2009, at 3:07 PM, Wietse Venema wrote:
Erick Calder:
On Sep 25, 2009, at 2:30 PM, Wietse Venema wrote:
<snip>
You can't replace the delimiter. That would break other people's
transit mail, among many things.
I'm not sure I understand... perhaps we're speaking of 2 different
things. what I mean is that when an e-mail first arrives at the
server, before it gets processed, it could be rewritten to use the
known delimiter i.e. a mail arriving for e/[email protected] could be
rewritten as [email protected] (since + is what postfix uses to
delimit)
On an infrastructure server, can't replace the delimiter. That
would break other people's mail.
oh, I think i get it. if server A is just relaying to server B, it
will get e/[email protected] and hand [email protected] to B. I'm not sure
I understand how that would break the mail (since [email protected]) is
valid and will still be received. of course, if B is configured to
use delimiter | then it will break since it will receive e
[email protected] when it expects e|[email protected] - but that is easily
fixed since server A knows whether it's relaying or delivering to a
local account, no? so the rewrite could happen for local deliveries
only.
On an end-node server, you can use a regexp map in one of the Postfix
address rewriting features that already exist.
I figured there was already some such capability. I'll need to
research (for my own purposes)
