On Aug 10, Rob Browning wrote
> Adrian Bridgett <[EMAIL PROTECTED]> writes:
>
> > I believe that exim wants a fully qualified address. Try putting this in
> > /etc/exim.conf:
> > qualify_domain = localhost
> > qualify_recipient = localhost
>
> I tried this, and it didn't help.
Have you got this in /etc/hosts? (I don't know if it should be there
though!):
127.0.0.1 localhost
> > mda "exim -bm %s "
>
> This fixes the problem, but according to the FAQ this is just masking
> some other problem with the SMTP listener. Any idea how to fix the
> listener?
Well here is a quote from the fetchmail FAQ (not that I understand it):
--cut-here--
By default, the exim listener enforces the the RFC1123 requirement that
MAIL FROM addresses you pass to it have to be canonical (e.g. with a
fully qualified hostname part).
This is a potential problem if the MTAs upstream from your fetchmail
don't necessarily pass canonicalized From and Return-Path addresses, and
fetchmail's "rewrite" option is off. The specific case where this has
come up involves bounce messages generated by sendmail on your mailer
host, which have the (un-canonicalized) origin address MAILER-DAEMON.
The right way to fix this is to enable the "rewrite" option and have
fetchmail canonicalize From and Return-Path addresses with the mailserver
hostname before exim sees them.
If you must run with "rewrite" off, there is a switch in exim's
configuration files that allows it to accept domainless MAIL FROM
addresses; you will have to flip it by putting the line
sender_unqualified_hosts = localhost
in the main section of the exim configuration file. Note that this will
result in such messages having an incorrect domain name attached to their
return address (your SMTP listener's hostname rather than that of the
remote mail server).
--cut-here--
Adrian
--
.signature in post
--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
[EMAIL PROTECTED] .
Trouble? e-mail to [EMAIL PROTECTED] .
