Actually, the forwarding of Bcc's do need header information,
specifically, who the message is to. In this case it is the recipient
of the Email.
procmail doesn't receive that information however once the Email is
delivered so that is my current problem.
It is also not correct to say To, Cc, Bcc are handled in the exact same
way. The header information for example is stripped in Bcc's.
Particularly with respect to procmail as:
* ^TO_user
{
:0 c
! [EMAIL PROTECTED]
}
will work, but
:0
* ^(Cc|To).*user
{
:0 c
! [EMAIL PROTECTED]
}
will not work.
-gc
Stephen Warren wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Gregory Carter wrote:
>
>> You are making the assumption that bcc copies of mail cannot be
>> forwarded. That is not correct.
>>
>
> No, I'm not.
>
> BCC'd mails can be forwarded just like any other mail; there is
> absolutely no difference in implementation for a To/CC/BCC'd email.
>
> Forwarding email doesn't need *any* header information *at all* from the
> original email. All you need to know is that an email was received (and
> the SMTP server and local delivery agent don't need headers for that),
> and also where to send the mail forward to (which also does not need
> header information).
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.2 (MingW32)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
>
> iD8DBQFF0zZhhk3bo0lNTrURAiKdAKDCOQLzOlY9MxlIcV1f40zcPNER/ACg5IZv
> nAe4hbEPlbHUd3en8Bk4E7o=
> =m+s6
> -----END PGP SIGNATURE-----
>
_____________________________________________
tmda-users mailing list (tmda-users@tmda.net)
http://tmda.net/lists/listinfo/tmda-users
