Geert Hendrickx:
> On Thu, Oct 22, 2009 at 01:40:56PM -0400, Victor Duchovni wrote:
> > On Thu, Oct 22, 2009 at 01:34:59PM -0400, Wietse Venema wrote:
> >
> > > Also, the RCPT TO command shows the address in raw form, so
> > > the same address may appear in different but equivalent forms:
> > >
> > > RCPT TO:<u...@example.com>
> > > RCPT TO:<"user"@"example"."com">
> >
> > The second is not RFC compliant, quoted-strings are only valid in the
> > local part of the address. The domain part is unquoted LDH, with IDNA
> > adding support for "xn--" prefixes on some labels.
> >
> > This said, I would really discourage any attempts to do domain
> > replacement with regexp command editing.
>
>
> You're probably right, there are too many different cases to be handled by
> simple regexpes. But a separate "rewrite olddomain to newdomain" feature
> (perhaps in cleanup(8) instead) would be really nice.
To avoid becoming a backscatter source,
1) The Postfix SMTP server needs a table that matches all recipient
addresses in the old domain.
2) The Postfix SMTP server needs a table that matches all recipient
addresses in the new domain.
Both tables can be generated from the same source, either with
scripting and plain files, or, if I am not mistaken, with clever
use of *SQL or LDAP queries.
Your suggested "rewrite olddomain to newdomain" feature does not
eliminate the requirement for 1) and 2).
If you can provide 1) and 2), then you can also provide the one-on-one
mapping from u...@olddomain to u...@newdomain.
Wietse
