[hashcash] procmail stuff (Re: hashcash doesn't pick the right resource during check?)

We should make a procmail howto / example from this.  Would marginally
simpler if -r took multiples and/or wildcards.

btw your match for the target string is wrong.  you have [0-9a-f]+

The reference implementation uses that lowercase hex, but basically
according to the internet-draft it can be any 7-bit printable,
non-whitespace and non : symbol.  There are other implementations for
example that use base64.

I'll use this too as I use procmail also with mutt, cool!

Adam

On Sun, Mar 07, 2004 at 08:35:52PM -0600, Kyle Hasselbacher wrote:
> I have procmail handling this normally, BTW.  This is the recipe I use,
> before my anti-spam measures, so that hashcashed mail can skip all the
> other filters:
> 
> # -c check
> # -q no output
> # -y valid tokens are good even if not fully checked
> # -X look for the X-Hashcash header
> # -e expiration time for tokens (default 28 days)
> # -d use a database to avoid double spending
> # -f where the double spending DB is.
> # -p purge the double spending database if it hasn't been done in that long
> # -b number of bits of work to require
> # -r "resource" to verify (e.g., kyle@xxxxxxxxxxx)
> :0
> * ^X-Hashcash: 
> 0:[0-9]+:[a-zA-Z0-9_+.-]+@(.+\.)?(hasselbacher\.org|toehold\.com):[0-9a-f]+$
> * ^X-Hashcash: 
> 0:[0-9]+:\/[a-zA-Z0-9_+.-]+@(.+\.)?(hasselbacher\.org|toehold\.com)
> * $? $HOME/bin/hashcash -c -q -y -X -e 31d -d -f $HOME/.tmda/hashcash.db -p 
> 10d -b19 -r '$MATCH'
> $DEFAULT

Other related posts: