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 Derek Martin):
{{{
On Wed, Oct 21, 2009 at 10:18:59PM -0000, Mutt wrote:
Arguably, even that shouldn't be an exception. If you want the mail
encrypted to yourself, then encrypt it to yourself. :) You can
encrypt a message to more than one person... I do exactly this
whenever I send encrypted mail. You don't have to specify yourself as
a recipient to do this; you can add it to your encrypt command, or (I
believe) even do it by default in your gpg options.
That is, I believe, exactly what my patch does. It forces Bcc to be
written to the fcc, but if you don't have one, there's nothing to
write... Right? :)
The argument has been made, and I happen to agree, that it is Exim's
behavior that doesn't make sense. The Exim folks took an interface
that had long been a defacto standard, and messed with it
significantly, but left it looking almost the same to the casual user.
Shame on them... violation of Principle of Least Surprise. That
said, e-mail programs need to work in the environment in which they
live. Obviously I think Mutt also needs to behave in a way that works
for any *reasonable* MTA. I believe the patch I provided does a
(slightly) better job of that than the one that was applied.
*THAT* said, I still think you can get what you want if you just set
write_bcc. Does that not work for you? If not, how does it fail, and
how are you sending mail? Answering that is probably much more
productive than complaining about what a given piece of software does
or does not do... ;-)
The next question (assuming write_bcc doesn't fix it for you) would
be, did you try applying the patch I provided in ticket 2111? If so,
does it solve your problem?
}}}
--
Ticket URL: <http://dev.mutt.org/trac/ticket/3343#comment:>
Mutt <http://www.mutt.org/>
The Mutt mail user agent