james-server-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Norman Maurer ...@byteaction.de>
Subject RE: RemoteDelivery and timeout
Date Wed, 21 Jun 2006 07:02:43 GMT
Hmm im right that the 10 minutes timeout is the time after which the
connection get closed if it was no activity there ? if thats the cause
we should at least set it to something smaller like 3 minutes.

bye
Norman

Am Mittwoch, den 21.06.2006, 02:55 -0400 schrieb Noel J. Bergman:
> Norman Maurer wrote:
> 
> > after checking for the default timeout of RemoteDelivery i notice that
> > it is 10 Minutes! Why it must be so high ? is that not a bit overkill ?
> 
> I agree, but ...
> 
> > +1 for change it the default to 2 minutes. Thats what other MTA also
> > use.
> 
> See my other reply.  There are two timeouts: one for establishing the
> connection, one for socket I/O.  The connection timeout default is set to 1
> minute.  Once we have established a socket, then the higher 10 minute
> default timeout is currently used for I/O on that socket.
> 
> 	--- Noel
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
> For additional commands, e-mail: server-dev-help@james.apache.org
> 
> http://217.195.2.164:8080/bytestor/servlet/bytestor/template/storedMail,SetStatusOneTime.vm?stored_mail_id=5315&password=Y8S56PXhBjjPAWvf4QVCEQmNr4GqwFjn3AVsn4D4
> !EXCUBATOR:1,4498ed5d43379516351391!

Mime
View raw message