[Pkg-exim4-users] edge exim4 *always* adds Sender: field?
Ken R. Dye
ken.r.dye at sbcglobal.net
Wed Oct 10 15:51:16 UTC 2007
mh+pkg-exim4-users at zugschlus.de said:
> > >
> > > Do you know how mh delivers the messages to exim?
> > >
> > execve("/usr/sbin/sendmail", ["sendmail", "-bs", "-odb", "-oem", "-om"], [/*
> > 46 vars */]) = 0
> > Sendmail is a soft link to exim4
> So, mh talks SMTP on a pipe to exim, which is a rather unusual method
> of delivering e-mail.
I changed the conf so it now just does an SMTP socket to localhost.
"sendmail" was the default.
> > > You commented out the settings that allow you to set your arbitrary
> > > sender, doing exactly the opposite what you want and what would be the
> > > default.
> > The commenting out did not appear to change anything other than what the
> > "Sender:" field that was being forcibly injected into the message contained.
> Are you positive that it is exim inserting the Sender:-Header?
> Try: swaks --pipe 'exim -bs' --from <your address> --to <other address>
> and see whether the generated message has a Sender header. If it
> doesn't, then you need to yell at mh, not at exim.
> > > You might want to read spec.txt chapter 44.16, or grep spec.txt for
> > > "Sender:". The documentation is rather verbose.
> > Yeah, just what I was trying to avoid.
> Running a mail server is rocket science, you cannot get along without
> reading docs.
Yes, I suppose that is necessary, especially when I insist on using
an early 1980's email system!
What tripped me up was my dicking w/the MAIN_FORCE_SENDER sendings,
which affected what the Sender: field was being set to...and not
the fact that *why* the Sender: field was being sent at all. Anti-forgery
default settings in MH started the initation of that field...exim4 was just
Thanks for your work on this code, and pointing me in the right
More information about the Pkg-exim4-users