Mutt should write Bcc: list in saved messages

[Marco d'Itri <md@…>]

Package: mutt
Version: 1.3.23-4
Severity: wishlist

[NOTE: this bug report has been submitted to the debian BTS as Bug#122173.
Please Cc all your replies to 122173@bugs.debian.org.]

From: Steve McIntyre <stevem@chiark.greenend.org.uk>
Subject: Mutt should write Bcc: list in saved messages
Date: Mon, 3 Dec 2001 01:21:48 +0000

Package: mutt
Version: 1.3.23-4
Severity: wishlist

Even if configured to not include a Bcc: header when sending mail (as
in the default config, so exim does not show it), mutt should still
write one in a locally-saved copy. I've just sent a mail to a large
list of people, and the only way of recalling the recipients was to
read the exim log.

-- 
Steve McIntyre, Cambridge, UK.                   stevem@chiark.greenend.org.uk
<a href=http://www.chiark.greenend.org.uk/~stevem/>My home page</a>
"Can't keep my eyes from the circling sky,                 +------------------
"Tongue-tied & twisted, Just an earth-bound misfit, I..."  |Finger for PGP key



>How-To-Repeat:
>Fix:

[Derek Martin <invalid@…>]

On Sat, Oct 15, 2005 at 10:32:35PM +0200, Alain Bench wrote:
> **** Comment added by ab on Sat, 15 Oct 2005 22:32:35 +0200 ****
>  At last a patch for this old bug, thank you very much Derek!

No problem.  FWIW, I solved this one by adding another parameter to 
mutt_write_rfc822_header(), which honestly I think is a little ugly.
A better approach would have been to use the existing mode parameter,
and define mode flags.  But the current usage of that parameter didn't
really allow for that without redefining how it is used...

I do think that's the right way to go, but I was reluctant to make
that change without discussing it first.  What I would actually do is
combine those last 3 int parameters into one flags parameter and
define macros for them...  If you maintainer types would prefer that
solution, I can probably hack that up tomorrow.

-- 
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.


--ew6BAiZeqk4r7MaW
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)

iD8DBQFDUbQqHEnASN++rQIRAie4AJ9yuGu/1bp+pxS3udJEznhsd9f67wCfTZ8m
hiAo1WuLShw8Vq8wR3aiJGY=
=3Ebc
-----END PGP SIGNATURE-----

--ew6BAiZeqk4r7MaW--

[ab]

At last a patch for this old bug, thank you very much Derek!
It works. And thanks for the report, Steve.
Upload patch-1.5.11.ddm.mutt_force_bcc_in_fcc.1, tag patch,
deduppe unform, add original submitter and Debian #122173 to
notifieds. Note #122173 was already closed last year after a
$sendmail stripping BCC script workaround permitting safely
to have $write_bcc=yes.

[brendan]

patch-1.5.11.ddm.mutt_force_bcc_in_fcc.1

[myon]

An updated patch can be found in http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=467432