[hashcash] Re: hashcash-sendmail daemonizes better.

  • From: Adam Back <adam@xxxxxxxxxxxxxxx>
  • To: hashcash@xxxxxxxxxxxxx
  • Date: Sat, 12 Jun 2004 09:52:30 -0400

I installed and am using it now.  Seems to work.  (Didn't have problem
before either tho).

I am thinking of trying out the 2nd program hashcash-request.

What I'm wondering is this: could one take previous sending (which
hashcash-sendmail sees as it creates hashcash) as an indicator that
you will send to that person again and put in
eg. .hashcash/recipients.  Next when a mail arrives (.procmailrc hook)
with I suppose From, Reply-To, or Cc in this set (and procmail could
probably do this) then call hashcash-request on receipt.

Or other suggestions on how to hook hascash-request in so that it does
not compute stamps for all incoming mail?


On Fri, Jun 11, 2004 at 10:37:41AM -0500, Kyle Hasselbacher wrote:
> Hash: SHA1
> About a month ago, the environment around my hashcash-sendmail changed, and
> it started getting SIGHUP from an external source.  It took me a while to
> even notice it, but it's lead me to two changes:
> 1. I now use SIGUSR1 to notify myself of new queue items instead of SIGHUP.
> 2. I call setpgrp() and setsid() to really get the parent process off my
> back after forking.  If that doesn't work, it whines in the log.
> I encourage current users to upgrade, but if you're not having a problem,
> don't worry about it.
> - -- 
> Kyle Hasselbacher | Ships are safe in harbor,
> kyle@xxxxxxxxxxx  | but they were never meant to stay there.
> Version: GnuPG v1.2.4 (GNU/Linux)
> iD8DBQFAydHF10sofiqUxIQRAmmPAKDvzAux06FJtAvb9DBv/aOlnsUcxQCgvVZO
> lLJIQl90XBbmxGDOq4ZaWcs=
> =pKHa

Other related posts: