On 2010-01-28 18:02, Sam Varshavchik wrote: > Dave writes: > >> bindv6only.conf in /etc/sysctl.d contains: >> >> # This sysctl sets the default value of the IPV6_V6ONLY socket option. >> # >> # When disabled, IPv6 sockets will also be able to send and receive IPv4 >> # traffic with addresses in the form ::ffff:192.0.2.1 and daemons >> listening >> # on IPv6 sockets will also accept IPv4 connections. >> # >> # When IPV6_V6ONLY is enabled, daemons interested in both IPv4 and IPv6 >> # connections must open two listening sockets. >> # This is the default behaviour of almost all modern operating systems. >> >> net.ipv6.bindv6only = 1 >> >> >> This was dropped without warning by a very inconsiderate Debian >> maintainer. It has no effect until you reboot. Then applications >> that put ipv4 addresses into ipv6 sockets start failing. Courier is >> one of these. >> >> I suggest you change it to 0 until Courier is fixed. > > IPv4-mapped IPv6 addresses are documented as part of the IPv6 > addressing structure. See section 2.5.5 of RFC 3513. > Hi Sam,
I tend to agree fully with you but it seams that the Debian maintainers do not :( http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=560238 ------------------------------------------------------------------------------ The Planet: dedicated and managed hosting, cloud storage, colocation Stay online with enterprise data centers and the best network in the business Choose flexible plans and management services without long-term contracts Personal 24x7 support from experience hosting pros just a phone call away. http://p.sf.net/sfu/theplanet-com _______________________________________________ courier-users mailing list [email protected] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
