On Tue, Jun 21, 2005 at 09:57:25PM +0100, Mark Baker wrote: > Julian Gilbey wrote: > > >Exim4 now correctly removes any Bcc: header, so maybe the default > > > >/etc/Muttrc should be reverted to the upstream version in respect of > >setting write_bcc. > > > > > According to the exim 4.4x manual, it only removes the Bcc: header if > called with the -t option, i.e. it behaves exactly the same in this > respect as every other version. > > So either a) you're mistaken about it being "fixed", b) the exim > documentation is wrong, or c) there is some debian specific > customisation, possibly something in the config file.
Oh. I got the report slightly wrong. 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. Therefore, there is no reason to switch off the write_bcc option and it would be good to leave it with its default on setting so that the saved messages have full headers. Julian -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
