Print Page | Close Window

Read timeout Error

Printed From: LogSat Software
Category: Spam Filter ISP
Forum Name: Spam Filter ISP Support
Forum Description: General support for Spam Filter ISP
URL: https://www.logsat.com/spamfilter/forums/forum_posts.asp?TID=5657
Printed Date: 01 November 2025 at 5:44pm


Topic: Read timeout Error
Posted By: Guests
Subject: Read timeout Error
Date Posted: 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.

 


Replies:
Posted By: Guests
Date 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??

 

 

 

 

Posted By: LogSat
Date 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


-------------
Roberto Franceschetti

http://www.logsat.com" rel="nofollow - LogSat Software

http://www.logsat.com/sfi-spam-filter.asp" rel="nofollow - Spam Filter ISP


Print Page | Close Window