On 31 Jul 2015, at 7:36, Christian Jaeger wrote:
On July 30, 2015 2:40:35 AM CEST, RW <rwmailli...@googlemail.com>
wrote:
The plugin is on by default and use_hashcash defaults to 1, but you
need to set hashcash_accept to an appropriate value
That's disappointing. For me that barely counts as "on by default". I
was thinking that implementing hashcash would help get my mail
delivered to at least the spamassassin users, but this means that no,
only to the subset that cares about configuring it.
As it should be. There is no default value that could be reasonable for
a broad range of sites and users for the commonplace neglect times of SA
installations. One of the features of hashcash that raises it a
millimeter above most other species of the naive conceptual genus of
"e-postage" is the ability of receivers to arbitrarily set their own
price AND to raise the price over time to compensate for Moore's Law and
botnet growth. If you are not prepared to actively manage a hashcash
deployment, it is not going to be useful and over time will reduce your
SA accuracy in the unlikely event that hashcash becomes popular enough
for spammers to notice.
John Levine wrote a definitive debunking of e-postage schemes including
hashcash over a decade ago (http://www.taugh.com/epostage.pdf) and
published an update (substantively unchanged) via Virus Bulletin in 2009
(https://www.virusbtn.com/spambulletin/archive/2009/03/sb200903-epostage.dkb?mobile_on=no).
All of his points against e-postage in general and hashcash specifically
have held up over time.
