[ On mail to virtual domains, the local part of an address is rewritten
but the domain isn't ]
>Now, the RECIPIENT environment variable is set to
>"[EMAIL PROTECTED]". Here is were the problem lies, RECIPIENT
>does not contain the actual recipient of the message, but some other
>address. This other address is not equivalent because it will not be handled
>in the same way by the qmail system, and may end up in a different mailbox
>than [EMAIL PROTECTED], the actual recipient.
No, that's how it's supposed to work, but like much of qmail, it could
be documented a lot better.
On any mail received in a .qmail file, you know that the local part is
relative to the local domain. Why? Because if it weren't, you
wouldn't have gotten it. On the other hand, the domain isn't
rewritten because that's how you tell whether the mail was really sent
to westegg.com (the virtual domain), or to w1.drh.net (the local
domain.) Knowing whether it came in via a virtual domain is important
when you have private domains in virtualdomains but not in rcpthosts
for the benefit of local users. (I have a mail to news gateway set up
that way, for example.)
A counter question is why rewrite the address at all, if we're going
to leave the domain alone anyway. I believe (having limited vision
into Dan's thought processes) that the reasoning is that if the mail
originated locally, it could have been sent either to the virtual
address [EMAIL PROTECTED] or directly to morgan-testforward, and
he wanted the .qmail scripts to work consistently either way. I agree
this last bit is debatable, but at least it's not gratuitous.
As to ezmlm working, I dunno, I'm a troglodyte, I still run majordomo
albeit with many fully virtualized virtual domains. Maybe someone
else can report on ezmlm+virtualdomain experience.
--
John R. Levine, IECC, POB 727, Trumansburg NY 14886 +1 607 387 6869
[EMAIL PROTECTED], Village Trustee and Sewer Commissioner, http://iecc.com/johnl,
Member, Provisional board, Coalition Against Unsolicited Commercial E-mail
