Well I think spamassassin has a config that allows you to specificy your individual and whole site (wildcard) email addresses that you consider yours for purpose of receiving hashcash. The big question is if we can put something reasonable as a default such that we can get spamassassin accepting hashcash by default for some proportion of people who never get around to editing the config. Adam On Fri, Nov 04, 2005 at 10:47:44AM -0500, Eric S. Johansson wrote: > Adam Back wrote: > >Well I did put some thought to site wide use of hashcash cmd line tool > ... > >domain name (or it doesn't hurt to make this assumption). Of course > >large ISPs with many soft hosted email accounts, they'll be using lots > >of MX records pointing at the same host. Unfortunately I don't think > >there is a reverse lookup on MX records to find which MX domains this > >IP serves. > > for the static *@blah.tld, use a site specific configuration file to > eliminate ambiguities like the bar.foo.com and bar.co.uk cases. just > spell them out in a file and then convert to a dbm file ala newaliases. > cheap and easy. speed up later > > otherwise, the querying entity would supply the entire email address and > no special lookup is needed. I would match from most specific to least. > > would you want a quality of match indicator? exact, partial (and > which), or none?