Hi,
What version of James are you using?
James 2.3.0

James 2.2.0 had bugs in spooling timings and often the send was delayed 10-60 seconds.
Sound pretty much like the problem I'm facing with 2.3.0.
The only option you have is to increase the number of spool threads / delivery threads: this way if the system can handle that you will get faster deliveries.
I have tried increasing the number of threads, but it didn't really help. In fact I am sending mails sequentially. I'm waiting for the result of the last mail before sending the next (it's some kind of batch processing via mail). Usually the mail is handled in sub-second time but occasionally it takes between 15-45 seconds until it is picked up from the spool.

I am using MySQL for spooling, could this be the culprit?

Any logfile I could watch? Any other tweak I could try?

Michael

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

Reply via email to