Bug#833296: exim4-config: dpkg-reconfigure exim4-config: misleading message
Mauro Salvini
mauro.salvini at smigroup.net
Thu Aug 4 07:54:29 UTC 2016
On Wed, 2016-08-03 at 13:49 +0200, Marc Haber wrote:
> On Wed, Aug 03, 2016 at 01:45:33PM +0200, Mauro Salvini wrote:
> > On Wed, 2016-08-03 at 10:44 +0200, Marc Haber wrote:
> > > What does getent hosts $IP for all your IP addresses say?
> >
> > getent hosts 127.0.0.1
> > 127.0.0.1 localhost
> >
> > getent hosts 127.0.1.1
> > 127.0.1.1 myhostname.mydomain.local myhostname
> >
> > getent hosts 10.0.xx.xx # LAN address
> > 10.0.xx.xx myhostname
>
> I would investgate this
>
> > getent hosts 10.0.yy.yy # WIFI address
> > 10.0.yy.yy myhostname
>
> and this. This should give a fully qualified output as well, I think.
>
Hi Marc,
I found some interesting at this page:
https://wiki.debian.org/PkgExim4UserFAQ
paragraph 1.2.3 references to:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=756224
libnss-myhostname is installed on my system (version
0.3-9).
After reading bug report discussion, I tried to remove myhostname
from /etc/nssswitch.conf:
#hosts: files myhostname mdns4_minimal [NOTFOUND=return] dns
hosts: files mdns4_minimal [NOTFOUND=return] dns
With this configuration, exim -bP | grep ^primary_hostname states:
primary_hostname = myhostname.mydomain.local
Message #114 in bug report points me to this.
So is libnss-myhostname the problem?
Regards
Mauro
More information about the Pkg-exim4-maintainers
mailing list