[Pkg-exim4-users] sporadic invalid helo -- setting primary_hostname

Jonathan Addleman jono at redowl.ca
Wed Mar 2 19:16:23 UTC 2016


On 02/03/16 01:23 PM, J G Miller wrote:
> At 12:29h, on Wednesday, March 02, 2016,
> in message <56D72307.6080900 at redowl.ca>,
> on the subject of "Re: [Pkg-exim4-users] sporadic invalid helo -- setting primary_hostname",
> Jonathan Addleman explained --
>
>   > Indeed. It is worrisome. I'm at quite a loss as to troubleshooting it
>   > though. It seems that hostname -f doesn't use gethostbyname() or
>   > getipnodebyname() (at least as far as I can see from a strace). Are
>   > there other command line tools that I could use to test things?
>
> Only thing I can think of for testing at the command line is writing a
> simple C program to use gethostbyname for your own host name.

That's what I feared...

I'm not using nscd, NIS, or bind9
nsswitch.conf has the default "hosts: files dns" line.

One thing that I thought *might* be related is that my hosts line showed 
two 127.0.0.1 lines, one for localhost, and another for the actual 
hostname and fqdn. Some googling showed that there are cases where that 
could be problematic.. I changed the hostname one to 127.0.1.1, in any 
case. Maybe it will fix something down the road.

> And despite the dire warning on the Debian setting up Exim4 instructions
> about not using MAIN_HARDCODE_PRIMARY_HOSTNAME. I have always set it on
> my heavily customized Exim4 setup (now on four machines) since 2005 or
> maybe earlier and never had a problem.

I'm leaning pretty heavily towards doing that now. Thanks for your help!

-- 
Jonathan Addleman - http://www.redowl.ca



More information about the Pkg-exim4-users mailing list