JWM wrote:
> With the default thread count of 1, one or more outbound emails to
> a non-well-behaved target mail server (e.g. outblaze...) can cause
> thousands of undelivered outbound emails to build up for days in
> the spool waiting for that one thread trying to send a couple of emails.
It should not be the case that one thread backs up for days to send a couple
of e-mails. Even with a 10 minute time out and many IP addresses. So that
needs to be checked, having nothing to do with interpretation of the proper
implementation of the RFC.
> One improvement is to increase the number of threads so one blocked thread
> won't shut the system down.
Sure ... unless you have a few mails going to that server, in which case you
might block on ALL threads going to that same server. Not a solution to the
problem.
> Another improvement is to reduce the timeout from 10 minutes to ~2
minutes.
You can do that right now in your config.xml.
> if James encounters a timeout situation and heads down the path of
> trying a bunch of ip addresses, have one delivery thread that is
> dedicated as the 'slow driver lane' thread.
Interesting idea, although then you need multiple thread pools: one for the
first type, and one for the retry type.
--- Noel
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
