🚀 go-pugleaf

In article <816695036snz@wash.demon.co.uk>
   John Washington <john@wash.demon.co.uk> writes:
>Is there anything I can do to get mail going out more reliably?
>Has anybody written a replacement SMTP client?

I'm sorry, I haven't any easy ideas about this.  One thing that might
help is to be able to do asynchronous DNS MX enquiries and queue
updates.  At present, the client seems to have only one thread for
enqueuing things, and doesn't proceed with the next until the previous
one is queued.  As you mentioned in the pub last night, this is no doubt
due to its desire to queue all messages for the same destination via the
same connection.  It would be an interesting experiment to rip that code
out ^[BBBBd4W carefully modify that area and see what happens.  

However, some remote SMTP servers might be unhappy about being
potentially blasted with 30 or more simultaneous single-message
connections - Demon's mail2news, for instance !  It might be necessary
to somehow limit connections to a single site again, or to introduce an
alternative form of per-site queue.

Another thing, again as you suggested, is to remove "smtp batch"
entirely.  I really cannot see who would want to use it, given that one
cannot tell whether the remote server accepts it until one sees the
bounce - by which time it is too late.  The command line option could be
left in, to prevent support calls about "unknown command", but the
setting merely ignored in the client.  This would also free up a little
code space for any desirable enhancements !

Mainstream KA9Q has, I understand, diverged rather from ours now.  Is
there a known place - FTP site or newsgroup - where other versions of it
live ?  Maybe there might be some ideas or fixes from other people.

Nick