Mailing List Archive

On Wed 04 Apr 2007 18:38:47 Scott Kitterman wrote:
> The libspf.org web site has been down for quite some time now and the
> libspf authors have been unreachable for even longer. I think it's time to
> remove libspf from the implementations page. Unless someone objects, I'll
> do it in the next few days.

If at the same time you could add RaSPF, which is pretty compliant and has
only one known bug (a memory leak), that'd be nice :-)

URL: http://raspf.blogsite.org

Best regards,
 
--
 ("\''/").__..-''"`-. .         Roberto Alsina
 `9_ 9  )   `-. (    ).`-._.`)  ralsina@kde.org
 (_Y_.)' ._   ) `._`.  " -.-'   KDE Developer (MFCH)
  _..`-'_..-_/ /-'_.'
(l)-'' ((i).' ((!.'   Buenos Aires - Argentina

Debugging is twice as hard as writing the code in the first place.
Therefore, if you write the code as cleverly as possible, you are,
by definition, not smart enough to debug it. --Brian W. Kernighan

-------
Sender Policy Framework: http://www.openspf.org/
Archives at http://archives.listbox.com/spf-discuss/current/
To unsubscribe, change your address, or temporarily deactivate your subscription,
please go to http://v2.listbox.com/member/?list_id=735

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Scott Kitterman wrote:
> The libspf.org web site has been down for quite some time now and the
> libspf authors have been unreachable for even longer. I think it's time
> to remove libspf from the implementations page. Unless someone objects,
> I'll do it in the next few days.

I second that.

Too bad libspf has left the market, but it's really not in a good shape...

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFGFrQ4wL7PKlBZWjsRAmrOAJ9FkQY78Ao59m3DT4rfG8HMMAvXjgCeM6Jr
JDCrQtCh7CluMZlSp01GE+U=
=Wyx0
-----END PGP SIGNATURE-----

-------
Sender Policy Framework: http://www.openspf.org/
Archives at http://archives.listbox.com/spf-discuss/current/
To unsubscribe, change your address, or temporarily deactivate your subscription,
please go to http://v2.listbox.com/member/?list_id=735

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

William Leibzon wrote:
> I think you should have some policy on delisting. My recommendation
> would be to send notice to last know email with CC to this and devel-
> list that software would be delisted in say 30 days and what should be
> remedied for it to still be listed (i.e. working website).
>
> If no response then delist.

James Couzens' last known e-mail address has been bouncing for many months.
His domain 6o4.ca is dead.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFGFrimwL7PKlBZWjsRAuqOAKCdaPTWYcCNBSRNQM1U905cWvCdjwCgqTxS
YutCTEcHRy3hKDQsVY0xgcQ=
=zO0t
-----END PGP SIGNATURE-----

-------
Sender Policy Framework: http://www.openspf.org/
Archives at http://archives.listbox.com/spf-discuss/current/
To unsubscribe, change your address, or temporarily deactivate your subscription,
please go to http://v2.listbox.com/member/?list_id=735

On Friday 06 April 2007 18:00, william(at)elan.net wrote:

> I think you should have some policy on delisting. My recommendation would
> be to send notice to last know email with CC to this and devel- list that
> software would be delisted in say 30 days and what should be remedied for
> it to still be listed (i.e. working website).
>
> If no response then delist.

The problem is that all of James' domains that we know of have expired, so
there's no way to contact them in this case.

I've been thinking this over and perhaps we should move stuff to a historical
section at the bottom (I'd put Mail::SPF::Query in that catagory too).

Scott K

-------
Sender Policy Framework: http://www.openspf.org/
Archives at http://archives.listbox.com/spf-discuss/current/
To unsubscribe, change your address, or temporarily deactivate your subscription,
please go to http://v2.listbox.com/member/?list_id=735

On Fri, 6 Apr 2007, Julian Mehnle wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Scott Kitterman wrote:
>> The libspf.org web site has been down for quite some time now and the
>> libspf authors have been unreachable for even longer. I think it's time
>> to remove libspf from the implementations page. Unless someone objects,
>> I'll do it in the next few days.
>
> I second that.
>
> Too bad libspf has left the market, but it's really not in a good shape...

I think you should have some policy on delisting. My recommendation would
be to send notice to last know email with CC to this and devel- list that
software would be delisted in say 30 days and what should be remedied for
it to still be listed (i.e. working website).

If no response then delist.

--
William Leibzon
Elan Networks
william@elan.net

-------
Sender Policy Framework: http://www.openspf.org/
Archives at http://archives.listbox.com/spf-discuss/current/
To unsubscribe, change your address, or temporarily deactivate your subscription,
please go to http://v2.listbox.com/member/?list_id=735

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Scott Kitterman wrote:
> I've been thinking this over and perhaps we should move stuff to a
> historical section at the bottom (I'd put Mail::SPF::Query in that
> catagory too).

Stuff that doesn't exist on the net anymore, such as libspf, doesn't even
deserve a mention in a "historic" section. Who cares about it if we
cannot even give a link to it? Or is there still some site (obviously not
any official one) providing libspf for download? (Or we could of course
host a copy ourselves. Should we?)

I agree about Mail::SPF::Query going to "historic" eventually, however I
don't think the time is there just yet. M:S:Q is still in active use by
several software packages, so please let me finish the Mail::SPF-based
M:S:Q 2.0 wrapper first.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFGFsgnwL7PKlBZWjsRAgrcAKC8Cy0uRuKGYMdEm/gou1ava4zCnwCgoE6F
uMenYOav4f+zHqiA7qU0LTU=
=JpxD
-----END PGP SIGNATURE-----

-------
Sender Policy Framework: http://www.openspf.org/
Archives at http://archives.listbox.com/spf-discuss/current/
To unsubscribe, change your address, or temporarily deactivate your subscription,
please go to http://v2.listbox.com/member/?list_id=735

On Fri, 6 Apr 2007, Julian Mehnle wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> William Leibzon wrote:
>> I think you should have some policy on delisting. My recommendation
>> would be to send notice to last know email with CC to this and devel-
>> list that software would be delisted in say 30 days and what should be
>> remedied for it to still be listed (i.e. working website).
>>
>> If no response then delist.
>
> James Couzens' last known e-mail address has been bouncing for many months.
> His domain 6o4.ca is dead.

I know at least one other address for him at the company he worked at
year ago and know few more ways to find people that you probably are
not familar with. I'll let you know if he answers.

--
William Leibzon
Elan Networks
william@elan.net

-------
Sender Policy Framework: http://www.openspf.org/
Archives at http://archives.listbox.com/spf-discuss/current/
To unsubscribe, change your address, or temporarily deactivate your subscription,
please go to http://v2.listbox.com/member/?list_id=735

On Friday 06 April 2007 18:22, Julian Mehnle wrote:
> Scott Kitterman wrote:
> > I've been thinking this over and perhaps we should move stuff to a
> > historical section at the bottom (I'd put Mail::SPF::Query in that
> > catagory too).
>
> Stuff that doesn't exist on the net anymore, such as libspf, doesn't even
> deserve a mention in a "historic" section. Who cares about it if we
> cannot even give a link to it? Or is there still some site (obviously not
> any official one) providing libspf for download? (Or we could of course
> host a copy ourselves. Should we?)
>
> I agree about Mail::SPF::Query going to "historic" eventually, however I
> don't think the time is there just yet. M:S:Q is still in active use by
> several software packages, so please let me finish the Mail::SPF-based
> M:S:Q 2.0 wrapper first.
>
OK, but currently M:S:Q is not listed (other than in the front matter on
reference implementations) at all.

Although the official source for libspf is no longer available, it's still
packaged in a number of distributions and shipped (Debian for one). I think
that maintaining the history of the project is important. It's not just
about the code that we might want to run today. Good, bad, or indifferent,
lipspf was the first C implementation and is part of the project's history.

Scott K

-------
Sender Policy Framework: http://www.openspf.org/
Archives at http://archives.listbox.com/spf-discuss/current/
To unsubscribe, change your address, or temporarily deactivate your subscription,
please go to http://v2.listbox.com/member/?list_id=735