Adrian Close writes:
With IPv6 enabled, Courier will use IPv6 sockets to connect to IPv4 addresses. See section 5.3 of RFC 2553:But it won't even attempt a connection to IPv4-only MX hosts, which kind of foils my evil plan for world domination...er... I mean IPv6 sweetness and light, with peace in our time... ;)Is this because it's trying to make IPv4 connections from IPv6 sockets?
Applications may use PF_INET6 sockets to open TCP connections to IPv4
nodes, or send UDP packets to IPv4 nodes, by simply encoding the
destination's IPv4 address as an IPv4-mapped IPv6 address, and
passing that address, within a sockaddr_in6 structure, in the
connect() or sendto() call.
That, at least in theory, how it's supposed to work.
Courier will certainly read IPv4 MX records with IPv6 enabled. If you run testmxlookup you should still be able to read IPv4 MX addresses just fine.Can we make this work somehow? It seems to me that a fallback to IPv4 operation would be handy (including IPv4 MX entries for dual-stack hosts would be useful too, in case they don't have SMTP/IPv6 support).
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
courier-users mailing list
[EMAIL PROTECTED]
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
