Read timeout Error |
Post Reply
|
| Author | |
Anna
Guest Group
|
Post Options
Thanks(0)
Quote Reply
Topic: Read timeout ErrorPosted: 12 June 2006 at 2:06am |
|
Hi, How can i increase "read timeout" of spam filter when it receives an email??? I have many inbound emails rejected because read timeout is reached. Measured it and appears to be very short in order of 1 minute. please help. A. I have thses ini parameters: ReadTimeout=480 IdleDisconnectMinutesTimeout=15 DNSTimeout=10000 QuarantineToDeliverCheckInterval=15 MaxMsgSizeForKeywordScan=128 any ideas much appreciated.
|
|
![]() |
|
Anna
Guest Group
|
Post Options
Thanks(0)
Quote Reply
Posted: 12 June 2006 at 2:13am |
|
Hi again, If it helps... i measured it again, timeout is reached exactly 60 seconds... give or take a few milli seconds. Just wondering....How come it is not 480 seconds as specified in ini file??? Am i doing something wrong??
|
|
![]() |
|
LogSat
Admin Group
Joined: 25 January 2005 Location: United States Status: Offline Points: 4106 |
Post Options
Thanks(0)
Quote Reply
Posted: 12 June 2006 at 7:24am |
|
Here's what we think is happening, but we need your confirmation to be more certain.
SpamFilter accepts the connection, and runs most of its IP-based tests to check it for spam. The remote server then sends the email's content, but SpamFilter does not see the traffic since "something" else is temporarily holding it. Once that "something" has done its job, the SMTP traffic is fofrwarded to SpamFilter. What is happening is that SpamFilter has a built-in timer to fight Denial of Service attacks. If it sees an incoming connection that does not transmit any data for 60 seconds, it disconnects it. The "something" could be a firewall and/or a virus checking software that wait for the whole email body to be received, scan it for harmful content, and if clean, pass it on to SpamFilter. The problem is that if the email is large, or if the remote server is on a slow connection, it may take the email more that 60 seconds to be received by the "something". Once it is received, SpamFilter will have already cut the connection, thus the failure occurs. If you're not able to change your network topology to solve this problem, the good news is that the timeout value SpamFilter uses is configurable via an option in the SpamFilter.ini file from version 2.0.1.358: // New to VersionNumber = '2.0.1.358'; {TODO -cNew : Added ReadTimeout ini parameter to allow user control of timeout when waiting for remote SMTP commands} In your SpamFilter.ini file, look for the follwoing line under the [server settings] section (or add it if it's not there): ReadTimeout=60 You can change the number of seconds to a higher value, 300-600 should suffice in most cases. Please let us know if this solves the problem |
|
![]() |
|
Post Reply
|
|
|
Tweet
|
| Forum Jump | Forum Permissions ![]() You cannot post new topics in this forum You cannot reply to topics in this forum You cannot delete your posts in this forum You cannot edit your posts in this forum You cannot create polls in this forum You cannot vote in polls in this forum |
This page was generated in 0.328 seconds.


Topic Options
Post Options
Thanks(0)


