Martin,
The disconnect most likely happens because SpamFilter has a 60 second timeout where, if not a single
byte of data has been received for 60 seconds, the session is
disconnected.
The good news is that this value
can be changed (by modifying the ReadTimeout value in SpamFilter.ini file), the bad is that there
may be a deeper problem.
We've run into the following
scenario with some users:
The company had an
antivirus/firewall in front of SpamFilter that intercepted emails before they
reached SpamFilter. If a remote user either sent an email with a large
attachment or had a slow connection, the firewall would hold/scan the email for
a long time (> 60 seconds) before passing it onto SpamFilter. SpamFilter
would thus disconnect the firewall before receiving the email. This issue was
easily fixed by increasing the timout value.
Another issue I've seen was with
the Internet Mail Connector in Exchange 5.5. We saw an install of Exchange 5.5
that had a bug in that it would not send the correct end-of-email sequence. All
emails are terminated with the sequence (a dot on a standalone
line):
<CR><LF>.<CR><LF>
in Hex characters this is $0D $0A $2E $0D $0A.
Exchange server would occasionally corrupt that sequence by replacing a 0D
with a 00:
$0D $0A $2E $00 $0A
Since the end of email sequence was incorrect, SpamFilter (and other
applications...) kept on waiting for the correct sequence, which Exchange never
provided, and thus all sorts of problems were occurring. Unfortunately we do not
know if the bug was ever fixed, as Exchange was upgraded to 2000 and the problem
disappeared.
Please let me know if any of these thoughts are of any
help.
------------- Roberto Franceschetti
http://www.logsat.com" rel="nofollow - LogSat Software
http://www.logsat.com/sfi-spam-filter.asp" rel="nofollow - Spam Filter ISP
|