Re: [Exim] HELO verification failure for localhost MUA acces…

Top Page
Delete this message
Reply to this message
Author: Peter Bowyer
Date:  
To: Exim Mailing List
Subject: Re: [Exim] HELO verification failure for localhost MUA access
Toralf Lund said:
> I just noticed that the following
>
>   warn    !verify = helo
>           message = Message sent with invalid HELO/EHLO ($sender_host_name
> [$sender_host_address] presented itself as $sender_helo_name)

>
>
> in "check_recipient" will produce
>
> X-ACL-Warn: Message sent with invalid HELO/EHLO (localhost [127.0.0.1]
> presented itself as [127.0.0.1])
>
> in all outgoing messages sent via "localhost". That's when using Mozilla
> client. What's the best way around this? Perhaps I don't need the HELO
> check when sending like this, but I do want it for incoming messages,
> and possibly also hosts the setup relays for...


It's easy enough to disable it for localhost (hosts = ! 127.0.0.1 for
example). But the problem is probably caused by inadequate DNS resolution
- maybe you've not got reverse resolution for 127.0.0.0/8 or something?

Try

host 127.0.0.1
host localhost

and see what shows up. Then tweak your DNS zone files / hosts file / other
resolution mechanism.

Peter