Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Message-ID: <42B7F2B6.9030104@familiehaase.de> Date: Tue, 21 Jun 2005 12:57:58 +0200 From: "Gerrit P. Haase" User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.8) Gecko/20050511 MIME-Version: 1.0 To: Herb Martin CC: cygwin AT cygwin DOT com Subject: Re: Exim 4.50 with Content filtering and SPF References: In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Herb Martin wrote: >>>It looks mostly like IPv6 stuff is causing the glitches. >> >>This is the problem with libspf2, making the IPv6 stuff >>conditional should do it, but I am not a programmer so I have >>not really an idea how to start, all the IP stuff is mixed >>together in several functions and it will be some work to do >>to divide it into IPv4 and IPv6. > > > Although I didn't look at this enough to even have > a right to an opinion, it occurred to me that SPF > really does need to be able to process an IPv6 format > address to calculate SPF correctly. libspf does not require IPv6 to be present. > Perhaps just digging up the correct .h file or the > correct structure settings is the right way to go -- > it's not like SPF actually sends any network data > other than querying DNS perhaps. > > But when the SPF/txt record comes back from DNS it > might have 'mechanisms' such as ip6: within it and > thus the address format for IPv6 will follow..... IPv6 is not supported with Cygwin, there are no headers. http://cygwin.com/acronyms/#SHTDI Gerrit -- =^..^= -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/