JWM wrote:
Noel,
Are yoy seeing a 10 minute figure? That would imply that the target
server
accepted the connection, but is not doing I/O on it.
This is a log snippit from an earlier post in this thread. Precisely 10
minute lockups....
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]
Well, it is the 10 minutes timeout.
If you telnet to port 25 of the 64.71.166.194 server you can see that
the connection is established but the 220 welcome message is never sent
by the remote server.
mail.com has 2 MX servers. The main MX server has 6 IPs in a multihomed
configuration. the second (backup) MX server has the same 6 IPs.
This means that *currently* at each attempt James run 12 connections
each one taking 10 minutes before timing out. So 2 hours to mark a
*TEMP* error attempt for a single mail.
This happens very often (I experienced this in past, too), so I think we
should at least give options to avoid this. Decreasing timeouts is one
thing, but you understand that it does not make sense to loose hours
testing 2 times 6 multihomed servers and do this things 15 times by
default. In our default that single mail would result in 6*2*15 total
attempts (180 attempts) each one keeping a thread busy for 10 minutes
(1800 minutes, more than a whole thread day). 1800 thread minutes for a
single mail as worst case default is not acceptable to me.
Stefano
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
