#3337: [Bcc header showing] Mutt + Exim
-----------------------
+----------------------------------------------------
Reporter: will177 | Owner: mutt-dev
Type: defect | Status: new
Priority: major | Milestone:
Component: mutt | Version: 1.5.18
Keywords: bcc, exim |
-----------------------
+----------------------------------------------------
Hi,
I got stung by the following mutt+exim issue recently:
http://sysmonblog.co.uk/2009/04/mutt-exim4-debian-unbuntu-and-bcc-
fail-
fix-included.html
which starts:
"Take a default Ubuntu/Debian install using the Mutt mail client (MUA)
then switch to exim4. You get the most monumental FAIL - your bcc
addresses will be included in the message to everyone else.
Dangerous and
embarrassing!
..."
This page does offer a workaround, but I think this is really a bug in
mutt that should be fixed. I cannot see why the Bcc information
should
EVER go out to all recipients.
I have spoken to the original designer of Exim, Philip Hazel, who is
now
retired, about this and he tells me the following, i.e. it is a mutt
bug.
"Exim will only remove Bcc headers when it is being used as a message
*submission* agent, that is, if the -t (I think it is) option is
used to
ask it to take recipients from header lines. In all other cases,
when Exim
is a transport agent,
it doesn't mess with headers. This has been argued before to be the
correct approach.
So, if mutt is calling Exim, not using -t, and
expecting it to remove headers, it is mutt's problem."
Given I want mutt to save sent emails with the Bcc information but not
send out the Bcc information to all recipients, I think that this is a
mutt bug. (i.e. write_bcc=no is not the answer here.)
I am using the sendmail -t and exim workaround mentioned in the URL
above
for now, but when I next upgrade I might forget to apply this
workaround
so I'll like mutt to be fixed, if you agree.
Thanks in advance.
--
Ticket URL: <http://dev.mutt.org/trac/ticket/3337>
Mutt <http://www.mutt.org/>
The Mutt mail user agent