> I have a virtual table:
>=20
> | address | goto |
> +----------------------------+------------------------+
> | m...@example.com | m...@example.com |
> | @example.com | postmaster |
> +----------------------------+------------------------+
>=20
> Now, mail going to sv...@example.com goes to the postmaster mailbox as=20
> expected, but the To: line has been rewritten as postm...@example.com=
.
Virtual rewriting does not affect the message headers, but canonical
rewriting does.
Quoting http://www.postfix.org/ADDRESS_REWRITING_README.html#virtual:
"The [virtual] mapping affects only envelope recipient addresses;
it has no effect on message headers or envelope sender addresses."
[...]
--=20
Magnus B=E4ck
mag...@dsek.lth.se
Yes.. thanks for clarifying; I noticed that prior to migrating from my old=
=20
system (which I did not host), mail headers would be as follows:
Return-Path: <jo...@example.com>
X-Original-To: sv...@whohasit.com
Delivered-To: sv...@whohasit.com
Instead of:
Return-Path: <jo...@example.com>
X-Original-To: sv...@whohasit.com
Delivered-To: postm...@whohasit.com
I realize the newer practice may be more accurate, but it just created issu=
es=20
with some clientside filters while testing and I can only suspect it will=20
effect system user filters once this is migrated into production... (they=20
might scream and moan).
I'll do some more research.
Thanks,
Bryan
On Friday 07 May 2004 14:42, Magnus B=E4ck wrote:
> On Friday, May 07, 2004 at 23:23 CEST,
>
> Bryan <postfix_lis...@whohasit.com> wrote:
> > I have a virtual table:
> > | address | goto |
> >
> > +----------------------------+------------------------+
> >
> > | m...@example.com | m...@example.com |
> > | @example.com | postmaster |
> >
> > +----------------------------+------------------------+
> >
> > Now, mail going to sv...@example.com goes to the postmaster mailbox as
> > expected, but the To: line has been rewritten as postm...@example.com.