Hmmm, I've already packaged libspf2 which is of course confusingly similar. I'm not really in strong contact with upstream, but is there a reason for these two separate libs?
* martin f krafft ([EMAIL PROTECTED]) wrote: > Package: wnpp > Severity: wishlist > > * Package name : libspf > Version : 1.0.0 rc4 > Upstream Author : James Couzens <[EMAIL PROTECTED]> > * URL : http://www.libspf.org > * License : see below > Description : official ANSI C sender policy framework (SPF) library > > libSPF is an ANSI[0] C implementation of the SPF[1] ("Sender Policy > Framework"). libSPF's focus is to be as small and as portable as > possible and to provide a working example of how SPF would ideally be > implemented for authors of MTA's and implementors of RFC's 2821 and 2822. > libSPF currently only implements[2] explicitly what is set out in the SPF > Internet Draft as it was sent off to the I-D archive ( > http://archives.listbox.com/[EMAIL PROTECTED]/200405/0128.html) of > which copy can be found at the libSPF website: > http://libspf.org/files/spf-draft-200405.txt -- Eric Dorland <[EMAIL PROTECTED]> ICQ: #61138586, Jabber: [EMAIL PROTECTED] 1024D/16D970C6 097C 4861 9934 27A0 8E1C 2B0A 61E9 8ECF 16D9 70C6 -----BEGIN GEEK CODE BLOCK----- Version: 3.12 GCS d- s++: a-- C+++ UL+++ P++ L++ E++ W++ N+ o K- w+ O? M++ V-- PS+ PE Y+ PGP++ t++ 5++ X+ R tv++ b+++ DI+ D+ G e h! r- y+ ------END GEEK CODE BLOCK------