Paul Gardiner a écrit : > Brian Evans - Postfix List wrote: >> Paul Gardiner wrote: >>> Has postfix just recently been updated to use IPv6 when present? >>> >> From http://www.postfix.org/IPV6_README.html: >> The first new parameter is called inet_protocols. This specifies what >> protocols Postfix will use when it makes or accepts network connections, >> and also controls what DNS lookups Postfix will use when it makes >> network connections. >> >> /etc/postfix/main.cf: >> # You must stop/start Postfix after changing this parameter. >> inet_protocols = ipv4 (DEFAULT: enable IPv4 only) >> inet_protocols = all (enable IPv4, and IPv6 if supported) >> inet_protocols = ipv4, ipv6 (enable both IPv4 and IPv6) >> inet_protocols = ipv6 (enable IPv6 only) >> >> By default, Postfix uses IPv4 only, because most systems aren't attached >> to an IPv6 network. > > Phew! All working again. Thanks so much Brian. Setting > inet-protocols = ipv4 made my mailx test work, but fetchmail then > starting failing with: > > fetchmail: reading message u...@host.domain:1 of 1 (2428 octets) (log > message incomplete)fetchmail: connection to localhost:smtp [::1/25] > failed: Connection refused.
in your fetchmailrc, set smtphost 127.0.0.1/25 so that fetchmail connects to 127.0.0.1 instead of ::1 (which is probably obtained by resolving localhost). > It looks like I've had postfix set up this way since I first used it. > I think fetchmail must have changed. Anyway, I disabled IPv6 completely > and deleted stray IPv6 entries from /etc/hosts, and now all is well > again. (It may be that on past installs of SuSE, I have deleted the > IPv6 entries from /etc/hosts, and I just didn't this time). > > Great support. I wish it was like this with things I've paid for. > > Cheers, > Paul. >
