Mailing List Archive

svn commit: rev 22094 - incubator/spamassassin/trunk/build
Author: jm
Date: Thu Jun 24 20:02:51 2004
New Revision: 22094

Modified:
incubator/spamassassin/trunk/build/3.0.0_change_summary
Log:
forgot hashcash in the change announcement mail

Modified: incubator/spamassassin/trunk/build/3.0.0_change_summary
==============================================================================
--- incubator/spamassassin/trunk/build/3.0.0_change_summary (original)
+++ incubator/spamassassin/trunk/build/3.0.0_change_summary Thu Jun 24 20:02:51 2004
@@ -27,7 +27,7 @@
databases of domains that advertise with spam.

- SpamAssassin now includes support for SPF (the Sender Policy Framework,
- http://spf.pobox.com/).
+ http://spf.pobox.com/) and Hashcash (http://www.hashcash.org/).

Downloading
-----------
Re: svn commit: rev 22094 - incubator/spamassassin/trunk/build [ In reply to ]
jm@apache.org writes:

> forgot hashcash in the change announcement mail

I think we should deactivate hashcash by default or remove it. I think
spammers have more CPU than me, this is just asking for some spammer to
make use of all that zombie CPU.

It was a nice idea (as you recall, I thought highly of it in 2003 too),
but I think it has been appropriately discredited.

Daniel

--
Daniel Quinlan
http://www.pathname.com/~quinlan/
Re: svn commit: rev 22094 - incubator/spamassassin/trunk/build [ In reply to ]
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


Daniel Quinlan writes:
> jm@apache.org writes:
>
> > forgot hashcash in the change announcement mail
>
> I think we should deactivate hashcash by default or remove it. I think
> spammers have more CPU than me, this is just asking for some spammer to
> make use of all that zombie CPU.
>
> It was a nice idea (as you recall, I thought highly of it in 2003 too),
> but I think it has been appropriately discredited.

- -1.

Bear in mind that it does nothing unless the user specifies
"hashcash_accept" for (one of) the addresses in the hashcash token.
There's no default accept list, so spammers can mint tokens for everyone
all over the internet without affecting a very large proportion of them.

I think that's very likely to restrict its use to nonspam senders.

- --j.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
Comment: Exmh CVS

iD8DBQFA289TQTcbUG5Y7woRAv+sAJ4+dOeakLiv+bvONBdd/whZfyx8dgCdGxUp
cTsuVENKuHbg/xgD81BiXso=
=4uCo
-----END PGP SIGNATURE-----