I'm unhappy with the way you closed that bug. Please reconsider. I've just tested it with mutt 1.5.15+20070515-1 (the latest in experimental) and exim4 4.67-1 (the latest in unstable). With the default configuration, which is for mutt:
write_bcc set smtp_url unset sendmail set to "/usr/sbin/sendmail -oem -oi" the combination of mutt and exim4 _will_ leak the BCC header to the final recipients. In other words, when Julian says: It seems that in older versions of mutt, any Bcc header would be passed to the sendmail program, whereas in 1.5.9-2 (and presumably later versions), the write_bcc option is only made use of when saving a message to a mailbox (in mutt_write_rfc822_headers called from mutt_write_fcc in sendlib.c), but not when being sent to sendmail. he is wrong, at least wrong about "later versions". This bug could be completely fixed in different ways: - set smtp_url to localhost by default (I'd dislike that) - apply the patch in http://permalink.gmane.org/gmane.mail.mutt.user/22947, dug out by Adam (my preferred solution), or a better one (e.g. putting a new configuration option write_bcc_fcc or write_bcc_sendmail). Alternatively, use a patch that does it the other way: *never* write the "BCC" header to sendmail, have write_bcc control whether it writes to fcc or not. - change mutt to use "sendmail -t -oi -oem" or "sendmail -ti -oem" (whatever works in all sendmail implementations) instead of "sendmail -oem -oi", assuming all sendmail implementations understand that (more work than it is worth?) Please apply solution 2 :-) -- Lionel -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
