-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Thu, Mar 04, 2004 at 05:04:57AM +0000, Jason R. Mastaler wrote:
>Kyle Hasselbacher <[EMAIL PROTECTED]> writes:
>
>> I didn't figure it out
>
>I didn't respond because I wasn't really clear what you were asking.
>I guess tmda-sendmail was waiting for my-sendmail to return, because
>otherwise you run the risk of losing mail.
Thing is, it HAD exited. I'd look in the process list and see a zombie
where it had been. Its child was still chugging away, and the Python
process above it didn't seem to notice it had croaked.
I looked through pipecmd in Util.py (which seemed to be what does this),
but I couldn't see any funny business.
>> but I changed my own scripts around so that it's no longer a
>> problem.
>
>In general, what problem are you trying to solve with all this hoopla?
Well, see below.
>> I now have hashcash in my TMDA-generated challenges using this
>> strategy. The hashcash-sendmail wrapper just writes to a queue, and
>> I have a separate hashcash-deamon that runs through it adding
>> hashcash to the messages and pushing them out to the real sendmail.
>
>Pretty groovy. Pretty...excessive. ;-)
Excessive is right. I may change my mind eventually, but it's a nice
experiment right now.
I have a phobia that my outgoing challenges are being caught by other spam
filters and not reaching their intended recipients. Hashcash is my
strategy to make them more hammy.
I want to do the same thing with my own outgoing mail.
The computer on which I do my email is a modest 400MHz. Computing 26-bit
hashcash (my target) takes eight minutes (though I've seen it take 20). I
don't want to wait around for that, and I also don't want the machine to
drown with five or six running at once (though they're not memory or disk
intensive). A queue is natural.
Since the time to compute is so long, NOT waiting for it so important.
Waiting after I hit "send" is excruciating. I might not mind making TMDA
wait when sending except that doing so causes Postfix to give up on it
("Command time limit exceeded" when it gets something it has to respond
to).
Once I got the queue business working, I put in some prioritization. I can
configure how much hashcash to send to an individual (e.g., I know X
doesn't do anything with hashcash, so I can cheap out when sending there).
I can guess how much time a message will take based on number of
recipients, and how much hashcash they each get. The daemon does the
cheapest messages first (thought it doesn't interrupt itself to do a cheap
one if it's in the middle of an expensive one). I have the sendmail
wrapper detecting challenges and designating them as ten times the expense
of a single recipient email (so they're pretty much always last-in-line).
I did the math on this, and if I'd been adding hashcash to my challenges
last month, my poor computer would have spent 30% of its life just
computing hashcash. That doesn't include my own outgoing email.
Anyway, if anyone else is interested in this hoopla, drop me a line. I
consider it a work in progress, but it seems to be working fine.
- --
Kyle Hasselbacher | "Withdrawing in disgust is not the same as apathy."
[EMAIL PROTECTED] | -- tarot card, "Slacker" (film)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
iD8DBQFAR2Nu10sofiqUxIQRAmcQAJ4yl4UwD6YW7tQ2i/1DRKgUaOmDGACg099C
OZXdJwVNY1qCECpT0gB9/wQ=
=JrcD
-----END PGP SIGNATURE-----
_________________________________________________
tmda-workers mailing list ([EMAIL PROTECTED])
http://tmda.net/lists/listinfo/tmda-workers
