Hi Florian, On Sun, Oct 14, 2007 at 08:34:06PM +0200, Florian Kulzer wrote: > On Fri, Oct 12, 2007 at 22:10:03 +0200, Salvatore Bonaccorso wrote: > > [...] > > ---(snip: README.Debian.gz)--- > > We no longer unset write_bcc in /etc/Muttrc. If your MTA does not strip Bcc: > > headers, edit /etc/Muttrc. (exim4 and postfix strip them, exim(3) does not.) > > We also no longer unset use_from and use_domain. Mutt will use the contents > > of /etc/mailname to determine the domain part of the From: header. > > ---(snap)--------------------- > [...] > > This is a snippet from my ~/.muttrc: > > set write_bcc > # create /etc/exim4/exim.filter with the line > # headers remove "Bcc" > # edit /etc/exim4/exim4.conf.template to add, early on, the line > # system_filter=/etc/exim4/exim.filter > # run "update-exim4.conf" and restart exim4 > > The comments describe what I used to do to make exim4 remove the bcc > headers. (I found these instructions on some website, I think.) However,
Thank you very much for your help. Yes I found probably the same webpage a while ago [0]. I was wondering, about the above comment in the README.Debian.gz, since it says, that exim4 strip them by default. So I don't find my missconfiguration for exim4. Do you have also any hint on this? > I do not know if this still works on Debian, because for some time now I > have been using mutt's built-in smtp engine to contact the smarthost > directly, bypassing exim4. This works very well, the bcc headers are > saved locally but are not transmitted to any of the recipients. The > syntax is very simple: Thank you. If it's not possible to find the error, i will try one of the two solution above, proposed by you! [0] http://groups.google.ch/group/comp.mail.mutt/browse_thread/thread/19ad3fe43f0a13bd/fe761fe3c66de646 Best regards, Salvatore
