Re: SpamAssassin / hashcash deployment stats?
[email protected] (Justin Mason) Thu, 03 Nov 2005 12:36:46 -0800
| Newsgroups | gmane.mail.spam.hashcash |
|---|---|
| Message-ID | <[email protected]> |
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Eric S. Johansson writes: > Adam Back wrote: > > Forwarding a question from Jeffrey Hantin: > > > >> I'm trying to sell the idea of adding hashcash stamps to > >> purchase-related notification email here but I'm getting some static > >> from management since apparently they've never heard of it. Any > >> idea if the huge portals (AOL, MSN, Yahoo, GMail) and huge ISPs > >> (Comcast, Earthlink, SBC, Cox, Bell South, Charter) will recognize > >> hashcash stamps? > > > > Is hashcash recognition turned on by default in SpamAssassin? > > > > Are there any stats or estimates of the percentage of email gets > > delivered thru SpamAssassin? > > > > > > btw As I said to Jeffrey in email, I think the application seems like > > is a great idea as its a common problem that your receipt after buying > > something online doesn't arrive and its because your spam filter ate > > it. Its also a nuisance for the company becuase then you call them up > > and waste their time trying to get confirmation of purchase. > > > > the last time I spoke with Justin about this (and I'm sure he will > correct me if I'm wrong) is that spamassassin had hashcash turned on by > default but it was set up to modify your score instead of a pass/fail > test. The bigger the stamp, the bigger the positive score. the Spam > assassin scoring model makes it possible for a stamped message to be > considered spam. On the other hand, you can always make a bigger stamp. Yep, that's the case. Also worth noting that most users will not have it set up by default; it requires a line of configuration (to tell it what stamp addresses you expect to receive stamps for). - --j. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (GNU/Linux) Comment: Exmh CVS iD8DBQFDanTeMJF5cimLx9ARAn1mAJ9QfVb3XjTbeCFGtHHTV1ttukvuNwCdHdgV Etxajm0ruTQHqOK+rzEukaQ= =MeGE -----END PGP SIGNATURE-----