http://bugzilla.spamassassin.org/show_bug.cgi?id=4619
------- Additional Comments From [EMAIL PROTECTED] 2005-10-15 01:45 ------- It's hard to say what IO::Socket::INET6 _should_ do when ipv6 is not available. Neither do I know what anything would do with no ipv4 available. I don't have a system I could test with in that configuration. Does anyone else? Part of the problem is that Net::DNS::Resolver does not do everything that we need, so we have a wrapper around it. Because of that we have code that has to be aware whether ipv6 is available, similar to some code in Net::DNS::Resolver. We can't just allow Net::DNS::Resolver to figure out if ipv6 is available and then ask it because it does not provide an API for asking that. We can request of the maintainer that he add a call, or that he change the semantics of force_ipv4 slightly to set it when the object determines that ipv6 cannot be used, but we don't have that now. Even if we did that, Net::DNS::Resolver takes force_ipv4 as an option and we still need a way to make that an option in SpamAssassin so that it can be set in Net::DNS::Resolver when it is needed. I will submit a request to the maintainer that Net::DNS::Resolver create a dummy socket to test if ipv6 is working and that he add some way to query the object to find out if it is supporting ipv6. Then those aspects of this patch would become obsolete and could be removed if we want to require that future version of Net::DNS. I think we still need it for now. Later, me may prefer to keep it in rather than require a newer versio of Net::DNS. That still leaves us needing a force ipv4 option. As to working with an ipv6-only system, let's create an RFE for that in Bugzilla and keep it in mind, perhaps determning what IO::Socket::INET and IO::Socket::INET6 and Net::DNS do with such a sytem, then figuring out what we need to do. I think that we need this patch now in order to work on systems that we can reasonably expect to encounter, and can deal with enhancements to Net::DNS::Resolver later. ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.
