<<< Date Index >>>     <<< Thread Index >>>

Re: storing the Bcc field in undisclosed-recipients messages



-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Friday, May 12 at 11:00 AM, quoth Pablo Marín Ramón:
>When I send a message to multiple, unrelated, recipients, I
>usually put my own address (or a fake address) as the To field
>and attach the true destinations in the Bcc field as a privacy
>practice.
>
>I store all my outgoing messages using the record variable, but
>when they are registered in the record mailbox they lose the Bcc
>field. I would like to keep this field in my local copy.

Mutt writes out the BCC header by default. The only reason it would 
not do so is if you have unset the $write_bcc variable. The only 
reason you should do that is if you have an MTA that does not strip 
off Bcc headers (e.g. exim4). Now, strictly speaking, mutt is allowed 
put the Bcc header in the FCC copy of the mail regardless of your MTA, 
but it looks like it doesn't if $write_bcc is unset (you may want to 
take that up with the mutt-dev list).

What MTA do you use? And why are you unsetting $write_bcc?

~Kyle
- -- 
Liberty is the only thing you cannot have unless you are willing to 
give it to others.
                                                -- William Allen White
-----BEGIN PGP SIGNATURE-----
Comment: Thank you for using encryption!

iD8DBQFEZHDXBkIOoMqOI14RAmhsAJ9iGdLPfpXqx4dojQ3acslMPixZNgCg3Flx
HoBcg2xcxXci2yfiju3G4r4=
=lUCy
-----END PGP SIGNATURE-----