Bug#261093: ITP: libspf -- official ANSI C sender policy framework (SPF) library

2004-07-27 Thread martin f krafft
also sprach Eric Dorland <[EMAIL PROTECTED]> [2004.07.26.0618 +0200]: > Hmmm, unfortunately I was away for the weekend and he seems to have > taken the page down :( He is realising that the polemic nature of the page did more bad than good. -- Please do not CC me when replying to lists; I read t

Bug#261093: ITP: libspf -- official ANSI C sender policy framework (SPF) library

2004-07-25 Thread Eric Dorland
* martin f krafft ([EMAIL PROTECTED]) wrote: > also sprach Eric Dorland <[EMAIL PROTECTED]> [2004.07.23.2003 +0200]: > > 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 l

Bug#261093: ITP: libspf -- official ANSI C sender policy framework (SPF) library

2004-07-24 Thread martin f krafft
retitle 261093 RFP: libspf -- sender policy framework (SPF) library retitle 261189 RFP: libsrs -- sender rewriting scheme (SRS) library thanks also sprach Colin Watson <[EMAIL PROTECTED]> [2004.07.24.1321 +0200]: > I have to say, that page entirely convinces me that its author is > a kook, and tha

Bug#261093: ITP: libspf -- official ANSI C sender policy framework (SPF) library

2004-07-24 Thread Henrique de Moraes Holschuh
On Sat, 24 Jul 2004, Colin Watson wrote: > On Sat, Jul 24, 2004 at 09:50:33AM +0200, martin f krafft wrote: > > also sprach Eric Dorland <[EMAIL PROTECTED]> [2004.07.23.2003 +0200]: > > > Hmmm, I've already packaged libspf2 which is of course confusingly > > > similar. I'm not really in strong cont

Bug#261093: ITP: libspf -- official ANSI C sender policy framework (SPF) library

2004-07-24 Thread Colin Watson
On Sat, Jul 24, 2004 at 09:50:33AM +0200, martin f krafft wrote: > also sprach Eric Dorland <[EMAIL PROTECTED]> [2004.07.23.2003 +0200]: > > 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

Bug#261093: ITP: libspf -- official ANSI C sender policy framework (SPF) library

2004-07-24 Thread martin f krafft
also sprach Eric Dorland <[EMAIL PROTECTED]> [2004.07.23.2003 +0200]: > 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? Well, apparently libspf is the established stan

Bug#261093: ITP: libspf -- official ANSI C sender policy framework (SPF) library

2004-07-23 Thread Eric Dorland
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 > Versi

Bug#261093: ITP: libspf -- official ANSI C sender policy framework (SPF) library

2004-07-23 Thread martin f krafft
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