On Wed, 6 Oct 2004, John R. Shearer wrote:
> I am having a problem with Exim rewriting the "To:" and "From:" headers in
> messages that are locally generated. If either of these two headers is
> missing a domain name then Exim is inserting the domain declared by
> "qualify_domain".
That is because RFC (2)822 specifies that addresses must always be fully
qualified. A message that contains unqualified addresses is
syntactically invalid. When a message is locally generated, Exim takes
on the task of fixing up problems like this, assuming it is being called
by broken MUAs.
> According to the spec the main configuration option "local_from_check=false"
> can disable this for the "From:" header, but A) it isn't, and B) there is no
> "local_to_check=false" option.
All that that option disables is the check to determine whether or not a
Sender: header should be added. As I read the spec, that it what it
says, but I will add an explicit statement in the next edition,
clarifying that it does NOT turn off the qualification fixup.
> # exim -d -v -f nobody@??? test1@??? << EoD
> > From: "Joe D. Spammer"
> > To: "Unlucky M. Alebox"
Those are both syntactically invalid header lines. Maybe you should
consider rejecting such messages out of hand so you never have to deal
with them? There is an ACL option to do that: "verify = header_syntax".
OR, now that I've remembered it, take a look at the -bnq command line
option...
--
Philip Hazel University of Cambridge Computing Service,
ph10@??? Cambridge, England. Phone: +44 1223 334714.
Get the Exim 4 book: http://www.uit.co.uk/exim-book
