Kyle Hasselbacher <[EMAIL PROTECTED]> writes: > What I meant was that the MUA expects an MTA to queue. On a > desktop, we assume there's a server, and we have to queue if we > can't reach it. Outlook has an outgoing queue, for instance. On a > server, there's queueing software already there (sendmail), and the > MUA expects it will just throw a message at the MTA, and the MTA > will queue.
Yes, but what if it takes a long time to queue? This is essentially what happens if you have tmda-sendmail or tmda-ofmipd add hashcash tokens. In the example I gave, Mail.app doesn't have a queue, but it does allow one to do additional work while it is transferring the message to the MTA. So, it is really doing the same thing your MUA is, it's just not making you sit there and watch it do it. > Of course, if I had a faster computer, there'd be much less > incentive to do all this. 8-) Possibly, although even on the fastest PC hardware available, waiting for hashcash tokens to mint when you send a message is annoying. I think if you use a serial MUA like you do that isn't likely to change its paradigm, the only option is some sort of custom queuing mechanism like you've designed. _________________________________________________ tmda-workers mailing list ([EMAIL PROTECTED]) http://tmda.net/lists/listinfo/tmda-workers
