Re: [Mutt] #3343: unset write_bcc removes BCC header in sent folder
#3343: unset write_bcc removes BCC header in sent folder copy
----------------------+-----------------------------------------------------
Reporter: chaoflow | Owner: mutt-dev
Type: defect | Status: new
Priority: major | Milestone:
Component: mutt | Version: 1.5.20
Keywords: |
----------------------+-----------------------------------------------------
Comment(by chaoflow):
Replying to [comment:2 Derek Martin]:
> (..)
> Assuming that behavior stands, then you should be able to get what you
> want by setting write_bcc.
I think a mail should be recorded in exactly the way I composed it (being
encrypted for me instead of the receiver, being a logical exception).
write_bcc therefore may not influence that and should only have an effect
on the mail that is sent out.
> In my opinion, the problem with this
> approach is that it doesn't take into account the possibility that a
> new MTA will come along that does not remove BCC headers, regardless
> of how a message is submitted (or a new release of an existing MTA
> that has a bug). It is better (i.e. safer), IMO, to always leave
> write_bcc unset, but force writing the header on fcc.
Mutt's behaviour here does not seem to make too much sense:
http://sysmonblog.co.uk/2009/04/mutt-exim4-debian-unbuntu-and-bcc-fail-
fix-included.html
--
Ticket URL: <http://dev.mutt.org/trac/ticket/3343#comment:3>
Mutt <http://www.mutt.org/>
The Mutt mail user agent