Re: mutt/2111: ESMTP patch: does not strip Bcc: header
The following reply was made to PR mutt/2111; it has been noted by GNATS.
From: Derek Martin <invalid@xxxxxxxxxxxxxx>
To: Mutt Developers <mutt-dev@xxxxxxxx>, bug-any@xxxxxxxxxxxxx
Cc:
Subject: Re: mutt/2111: ESMTP patch: does not strip Bcc: header
Date: Fri, 14 Oct 2005 13:24:01 -0400
--kfjH4zxOES6UT95V
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
On Fri, Oct 14, 2005 at 07:14:16PM +0200, Nicolas Rachinsky wrote:
> * Derek Martin <invalid@xxxxxxxxxxxxxx> [2005-10-14 11:48 -0400]:
> > So the bottom line is users should unset write_bcc if they don't want
> > the Bcc headers to appear in the message, and I think probably that
> > should be the default in Mutt, since the average user will not even
> > know what MTA they are using, never mind how it behaves WRT Bcc
> > headers, and write_bcc=no is by far the safest default.
>
> The problem with unsetting write_bcc is IIRC that then the header
> won't appear in the fcc folder. And sometimes it's good to be able to
> lookup who got the mail via Bcc.
I totally agree... but the only way to solve this without also
possibly compromising the privacy which the Bcc is supposed to afford,
is to have mutt treat the fcc differently (i.e. write the Bcc line
regardless of $write_bcc when writing the fcc). At the moment, it is
not capable of doing that, IIUC.
Now that I think about it, I believe that is the "correct" behavior
which mutt should exhibit. If I have the time this weekend, I'll hack
up a quick patch to make mutt do this.
--
Derek D. Martin http://www.pizzashack.org/ GPG Key ID: 0xDFBEAD02
-=-=-=-=-
This message is posted from an invalid address. Replying to it will result in
undeliverable mail. Sorry for the inconvenience. Thank the spammers.
--kfjH4zxOES6UT95V
Content-Type: application/pgp-signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)
iD8DBQFDT+mwHEnASN++rQIRAgBoAJ9PGrJ7tCszLGubEVqVBvjqP8RgzACfS/SB
pFLkEcQzl60vDb0l/v1GeSo=
=KtlB
-----END PGP SIGNATURE-----
--kfjH4zxOES6UT95V--