At 16:46 2000-10-04 -0600, Jason Cox wrote:
That really stinks then. I've noticed that neither Imail, Hotmail, AOL, nor
YahooMail add the headers necessary for procmail to process BCCs. That's a
rather large chunk of the Internet Mail population. Anyone know of another
work-around other than just not using procmail?
Let me try that again. *YOUR* MTA (that is, the "sendmail", "qmail" or
whatever app running on the mail server where procmail is being run) needs
to be adding this header. NOT the sender's MTA.
This CAN be done, it's just a config issue at the mail administrator's
level, not a user's level.
If your MTA doesn't add headers for mail which is being delivered for a BCC
(such as an X-Envelope-To header), you're generally going to be out of
luck. It certainly isn't procmail's fault -- if the info isn't part of the
message, you'll be hard pressed to determine it with any other tool you
might try to use.
Perhaps you should go to square one and review your message headers looking
for where _YOUR ADDRESS_ appears in them. Sometimes (if only ONE alias
within your virtual domain, etc receives the message), the Received: lines
will contain your address:
My procmail messages include:
Received: from nets5.rz.rwth-aachen.de (nets5.rz.RWTH-Aachen.DE
[220.127.116.11]) by mail.professional.org (8.10.0.Beta6/8.10.0.Beta6)
with ESMTP id e94MldS12236 for <PSE-L(_at_)mail(_dot_)professional(_dot_)org>; Wed, 4 Oct
2000 15:47:40 -0700
X-Envelope-To: is added by by specific config to my sendmail, while the
Received line has contained such references from even before when I
configured sendmail to include the envelope information.
Occasionally, I'll get a message that doesn't include this information, and
invariably, those turn out to be spam messages.
Please DO NOT carbon me on list replies. I'll get my copy from the list.
Sean B. Straw / Professional Software Engineering
Post Box 2395 / San Rafael, CA 94912-2395
procmail mailing list