Tom Hendrikx:
> Wietse Venema wrote:
> > Tom Hendrikx:
> >> Hi,
> >>
> >> After setting up postfix up on a ipv4/ipv6 dualstack machine I'm seeing
> >> the following issue: connections on 127.0.0.1 (where my content_filter
> >> re-injects mail) are logged as:
> >>
> >> 010-01-13T22:51:07+01:00 meredith-vmail postfix/smtpd[4772]: warning:
> >> 127.0.0.1: address not listed for hostname ip6-localhost
> > 
> > Given the client IP address 127.0.0.1, Postfix gets the name
> > ip6-localhost, but that name does have the address 127.0.0.1.
> > 
> >> After some time reading google and debugging this is what I found out:
> >> - /etc/hosts contains the following stuff regarding localhost (in the
> >> specified order):
> >> ::1 ip6-localhost ip6-loopback
> >> 127.0.0.1 localhost
> > 
> > And indeed. Name ip6-localhost does not list address 127.0.0.1.
> > 
> > Somewhere, you have a mapping from 127.0.0.1 that returns ip6-localhost,
> > and that mapping is screwing things up, because 127.0.0.1 is not
> > listed as an address for ip6-localhost.
> > 
> 
> I got as far as this conclusion too, which got me checking for the
> contents of /etc/hosts. Since I can influence the lookup results easily
> by shuffling the contents of /etc/hosts, can I conclude that this is an
> issue with my glibc?

Obviously, there is no 127.0.0.1 <-> ip6-localhost mapping in /etc/hosts.

Therefore, when Postfix gets ip6-localhost when it asks the name
for 127.0.0.1, then that information did not come from /etc/hosts.

You can tweak your /etc/hosts until the cows come home, or you can try
to find out were that 127.0.0.1->ip6-localhost is coming from.

        Wietse

Reply via email to