Glynn Clements wrote:
>
> shivanand prabhu tendulker wrote:
>
> > We are downloading our mails from a remote server
> > using POP3 protocol and then distributing the mails
> > using procmail. But procmail cannot process the Bcc
> > copies of mail.
>
> Of course it can't. Any BCC: headers will be stripped out by the first
> MTA which sees them. The whole point of "BLIND Carbon Copy" is that
> the other recipients DON'T get to see who you BCC'd the message to.
>
> Why would you want these headers anyhow? Mail routing is supposed to
> be based upon the ENVELOPE recipient address, which isn't going to be
> found in any of the normal recipient headers (consider the messages
> which you receive from this list; your email address doesn't appear in
> any of the normal recipient headers).
Hi
this is not completely true. My sendmail environment stores the
envelope field (rcpt to:) in the Received:-context in a line like
(in my case):
for <[EMAIL PROTECTED]>
See an example below.
This is not a privacy violation in the BCC-case, since only the
intended recipient gets this message, and the last mta anyway
needs to know, who this message was for.
If you can, configure your last mta (or let it configure) to store
a similar line in the header and use procmail against this line.
This even works in a commercial environment: I've created a
package that works like that for the biggest Swiss ISP.
Regards
Emmerich
---------- Header begin -----------------------------------
Return-Path: <[EMAIL PROTECTED]>
Received: from post.relayer.ecz (emm@localhost [127.0.0.1])
by eggler.ch (8.8.8/8.8.8) with SMTP id MAA11468
for <[EMAIL PROTECTED]>; Thu, 11 Nov 1999 12:49:29 +0100
^^^^^^^^^^^^^^^^^^^
.... (more) ...
-
To unsubscribe from this list: send the line "unsubscribe linux-net" in
the body of a message to [EMAIL PROTECTED]
