-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Fri, Mar 05, 2004 at 07:46:37PM -0700, Jason R. Mastaler wrote:
>Kyle Hasselbacher <[EMAIL PROTECTED]> writes:

>> 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.
>
>You might consider adding Habeas SWE headers to your challenges then.

I thought of that, but I'm not sure a challenge meets their "Compliance
Standard."  Using Habeas means making some statement about my email which
perhaps not everyone agrees with.  I'd rather just avoid it than have a
possible dispute with possible legal ramifications.

I see Habeas as meaning "you want to get my mail" (or maybe "I promise this
isn't unwanted") while hashcash means only "I want you to get my mail."

>> Since the time to compute is so long, NOT waiting for it so important.
>> Waiting after I hit "send" is excruciating.
>
>This is something that should be addressed in your MUA.  [...]

That sounds nice, but, well, it isn't.  If it were, I'd be worried about
how my MUA handled the case where there are many of them running at once.
Since I started queueing things, I've seen as many as four in the queue at
a time.  I wouldn't want them all duking it out for the processor at once,
and I'm don't know if the MUA will queue or just fork.  Come to think of
it, 'round these parts, MUAs don't do that--they expect to have an MTA that
does it for them.

>> 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).
>
>This is configurable in Postfix via the `command_time_limit'
>parameter.

That's helpful, thanks.  I probably won't use it, though.  I really DON'T
want lots of hashcash minting going at once.  I really DO want them to go
single file through the CPU.

Incidentally, since I last wrote, I implemented interrupting in the
daemon side of my little system.  It can use STOP and CONT signals to
interrupt low priority tasks with high.  This way the stuff I've designated
to be more important (or fast) always goes as quickly as it can.

>BTW, a hashcash mailing list has recently cropped up if you're
>interested.  http://www.hashcash.org/list/

Thanks!  I'll look at that.
- -- 
Kyle Hasselbacher | "Don't go around saying the world owes you a living.
[EMAIL PROTECTED]  | The world owes you nothing.  It was here first." -- M. T.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFASUop10sofiqUxIQRAqocAJ9PEYAme/z5+sd6qtUGqjZw0RpEOgCfTGpj
c/dhEp53obaWi2bBw0CUD6M=
=fPbW
-----END PGP SIGNATURE-----
_________________________________________________
tmda-workers mailing list ([EMAIL PROTECTED])
http://tmda.net/lists/listinfo/tmda-workers

Reply via email to