Bug#304718: [EMAIL PROTECTED]: Bug#304718: mutt: exim4 deletes bcc field, so maybe it's time to set write_bcc?]

Julian Gilbey [EMAIL PROTECTED] wrote: 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

Bug#304718: [EMAIL PROTECTED]: Bug#304718: mutt: exim4 deletes bcc field, so maybe it's time to set write_bcc?]

On Tue, Jan 03, 2006 at 12:14:28AM +, Adam M. Costello wrote: Julian Gilbey [EMAIL PROTECTED] wrote: 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

Bug#304718: [jdg@debian.org: Bug#304718: mutt: exim4 deletes bcc field, so maybe it's time to set write_bcc?]

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

Bug#304718: mutt: exim4 deletes bcc field, so maybe it's time to set write_bcc?

On Fri, Apr 15, 2005 at 09:39:11AM +0200, Marco d'Itri wrote: On Apr 15, Julian Gilbey [EMAIL PROTECTED] wrote: (2) It would seem a shame to conflict with exim 3.x for such a minor matter. How about, on clean install of mutt, doing something The exim maintainers could have fixed this

Bug#304718: mutt: exim4 deletes bcc field, so maybe it's time to set write_bcc?

On Fri, Apr 15, 2005 at 12:45:59AM +0200, Marco d'Itri wrote: severity 304718 normal thanks On Apr 15, Julian Gilbey [EMAIL PROTECTED] 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

Bug#304718: mutt: exim4 deletes bcc field, so maybe it's time to set write_bcc?

On Apr 15, Julian Gilbey [EMAIL PROTECTED] wrote: (2) It would seem a shame to conflict with exim 3.x for such a minor matter. How about, on clean install of mutt, doing something The exim maintainers could have fixed this stupid little details in all these years, it's not like this is my

Bug#304718: mutt: exim4 deletes bcc field, so maybe it's time to set write_bcc?

Package: mutt Version: 1.5.6-20040907+3 Severity: minor 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. Julian -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of

Bug#304718: mutt: exim4 deletes bcc field, so maybe it's time to set write_bcc?

severity 304718 normal thanks On Apr 15, Julian Gilbey [EMAIL PROTECTED] 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. Finally! On which exim versions should mutt conflict? --