Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
From:	"Herb Martin" <HerbM AT LearnQuick DOT Com>
To:	"'Gerrit P. Haase'" <gerrit AT familiehaase DOT de>, <cygwin AT cygwin DOT com>
Subject:	RE: Exim 4.50 with Content filtering and SPF
Date:	Tue, 21 Jun 2005 04:57:13 -0500
MIME-Version:	1.0
In-Reply-To:	<42B7D93C.6060109@familiehaase.de>
X-Spam-Flag:	NO
X-Spam-DCC:	:
X-Spam-Pyzor:	Reported 0 times.
Message-ID:	<EEBBA673245@mail.learnquick.com>

> > 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.

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.....

--
Herb


--
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/

- Raw text -