On 06/08/2012 11:03 AM, Wietse Venema wrote:
> inet_interfaces = all
> inet_protocols = all
Please show "postconf -n" output instead of main.cf.
Good idea, this is from "postconf -n":
inet_interfaces = all
inet_protocols = ipv4
Curious. If I strace it it doesn't seem to make any socket() calls but
that may just be something about how postconf works. I will try stracing
postfix itself.
It doesn't look like the problem is a lack of IPv6 support compiled in.
What is the evidence for that claim?
There are no errors parsing other IPv6 addresses in main.cf,
specifically the mynetworks setting. Also, after my previous email I
compiled the inet_addr_local tool mentioned in the IPV6_README using the
same build server/process that built postfix, and it does indeed report
all of the IPv6 addresses on the system:
[root@mx1 ~]# /usr/libexec/postfix/inet_addr_local
/usr/libexec/postfix/inet_addr_local: name_mask: all
/usr/libexec/postfix/inet_addr_local: inet_addr_local: configured 4
IPv4 addresses
/usr/libexec/postfix/inet_addr_local: inet_addr_local: configured 5
IPv6 addresses
127.0.0.1/255.0.0.0
72.37.225.168/255.255.255.0
10.0.0.168/255.255.255.192
172.24.1.168/255.255.255.0
::1/ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff
2001:4978:f:839a::10a8/ffff:ffff:ffff:ffff::
fe80::216:3eff:febf:4ffd%eth0/ffff:ffff:ffff:ffff::
fd30:d1b:589a:1::10a8/ffff:ffff:ffff:ffff::
fe80::216:3eff:fecb:5370%eth1/ffff:ffff:ffff:ffff::
http://partiallystapled.com/~gxti/trash/2012/06/main.cf.txt
404 file not found.
According to my access logs, someone retrieved "main.cf" instead of
"main.cf.txt". I named it the latter so that when browsed to it displays
in the browser instead of attempting to download it.
Thanks for looking.
-- m. tharp
