Hi,

I use James 2.1 in Linux, and if I set the retry delay to a minute or
something
and use multiple threads and send a few messages to a domain with
misconfigured
MX records (so pointing to IPs that do not exist)

James of course gets Connection timeout errors.. but then it sometimes takes
a long time resuming to the next retry. Eventually it will bounce it but it
is to slow..
I have also installed the windows version, and windows doesn't resume *at
all*
after 1 retries.....

Any idea's what could cause this..
Thanks in advance,

Ray


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to