It's sending now. But I still get lock ups for 10 minutes at a time. It is
apparently locking up on a bad server, then trying the next server in the
list, etc. But the world halts 10 minutes at a time, and James does nothing
at all outbound during that time.
I can see if I got a bunch of spam bounces to bad servers, with perhaps 3 or
4 mail servers listed for the domain, I could be hung up 30-40 minutes per
single email. This can't be right, can it?
Questions:
1) Is it working as designed that when a server is down, the outbound
processing halts until a 10-minute timeout?
2) Where is that 10 minute timeout specified? I can't find it anywhere in
the config.
Here is an example of where it locked up for 20 minutes trying to send one
email.... After finally timing out on 2 servers it finally successfully
connected to the third server and sent it.
770: 16/06/06 15:20:48 INFO James.Mailet: RemoteDelivery: Attempting
delivery of Mail1150406666744-21082-to-mail.com to host
mail-com.mr.outblaze.com. at 208.36.123.68 to
[EMAIL PROTECTED]
834: 16/06/06 15:30:49 INFO James.Mailet: RemoteDelivery: Attempting
delivery of Mail1150406666744-21082-to-mail.com to host
mail-com.mr.outblaze.com. at 64.71.166.194 to
[EMAIL PROTECTED]
877: 16/06/06 15:40:50 INFO James.Mailet: RemoteDelivery: Attempting
delivery of Mail1150406666744-21082-to-mail.com to host
mail-com.mr.outblaze.com. at 64.71.166.196 to
[EMAIL PROTECTED]
878: 16/06/06 15:40:56 INFO James.Mailet: RemoteDelivery: Mail
(Mail1150406666744-21082-to-mail.com) sent successfully to
mail-com.mr.outblaze.com. at 64.71.166.196
_________________________________________________________________
Express yourself instantly with MSN Messenger! Download today - it's FREE!
http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
