Quoting Peter Cavender ([EMAIL PROTECTED]):
> haha - no, I just host several domains for third parties, and the 
> people on domain3 ask why domain1 shows up in their mail headers... 
> Just trying to make my mail services *completely* virtualized.
> 
> People at local-bapist-church.org wouldn't want hot-sex-pics.com in 
> their mail headers. ;-)

Well, how would that be possible?  Non-standard virtual domains set
up?

Example:

You have mail.example.com as MX for virtual.com, which is in
virtualdomains as "virtual.com:joe".

In ~joe you have .qmail-joe.

Mail sent to [EMAIL PROTECTED] will have a delivered-to header
like so:

Delivered-To: [EMAIL PROTECTED]

Unless you have set up your virtualdomains in some way I'm not aware
of, it should be irrelevent what other virtual domains you have
configured.  Maybe you can share this tidbit.  We host quite a few
virtualdomains, I must say, and don't have your particular problem.

> >Doesn't the Received header also mention what your domain name is?
> 
> Not an issue for me - I only have incoming POP boxes, no relaying.

Well, did you hack qmail-smtpd.c to not add a Received header to the
top of each message?  How does email get delivered to your POP boxes
from the Internet, if not via qmail-smtpd or some other SMTP daemon
that follows RFCs?  No delivery from via SMTP at all, maybe?

> >Hmmm, but what program will you use to actually do the delivery?
> >You don't mention what mailbox format you're using.
> 
> Vanilla Maildir delivery on local machine.

Maybe you just need to install procmail, get the maildir patches from
www.qmail.org (are they still needed? I can't remember) and use
formail to cut out that header (a la formail -I) from the user's
.procmailrc.  Again, though, I would caution against removing
Delivered-To.

Aaron

Reply via email to