Stephan,
For now the workaround is to set the timeout to much longer in the SMTP
handler. The danger of setting the timeout too high is that if you have
someone errantly connecting to your server (or remotely getting stuck during
delivery), you'll have a lot of extra threads waiting for data that's never
coming.
What I intend to do is add a special InputStream in the SMTP handler so that
the timeout will get reset every few kb that has been sent. This way, as
long as the server is still receiving data at some reasonable rate (I'm not
sure what's reasonable... maybe 14.4kbps, so 1k/s??), then the connection
will not get timed out.
Serge Knystautas
Loki Technologies - Unstoppable Websites
http://www.lokitech.com
- Original Message -
From: Stephan Schiessling [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Saturday, November 17, 2001 8:09 AM
Subject: connectiontimeout problem
James2.0a2 denied to receive emails which take more than 6 minutes to
transfer.
(Depending on speed of internet connection, this may be the case for
emails with size 0.5 MB).
The timeout-counting starts if DATA section starts, so it is not
a timeout, which starts, when socket has no data !
I think the default installation of james (means: only a few things in
james/conf/config.xml are changed)
should not have this hidden limitation.
Therefore I suggest to set this connectiontimeout value (connectiontimeout
in handler in smtpserver)
to a much higher value, just for the default installation.
Bye,
Stephan Schiessling
[EMAIL PROTECTED]
NB: I already sent this message to this mailing list yesterday, and it was
sent successfully.
But I didn't get it back !?
--
To unsubscribe, e-mail:
mailto:[EMAIL PROTECTED]
For additional commands, e-mail:
mailto:[EMAIL PROTECTED]
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]
