timeout connection with Novell Groupwise
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=5917
Printed Date: 14 July 2025 at 3:59pm
Topic: timeout connection with Novell Groupwise
Posted By: Dan B
Subject: timeout connection with Novell Groupwise
Date Posted: 11 December 2006 at 3:58pm
|
Has anybody run into this issue? A customer of ours has a DSL connection running their own mailserver. They have their MX records pointing to our SpamFilter servers (primary & backup) so incase their DSL, or router, etc goes down and after scanning we redirect their outbound mail connection from port 25 to 20025 to connect to their Novell box. We are seeing this happen more often than not. That the SF servers will stop connecting to it and their mail gets queued on the SF servers. The retry is set for 5 mins and SF is showing that it's trying and trying and trying while the Novell Engineer monitors the Groupwise connections and does not see any connections from our SF servers. We stop and restart the service and then the queued mail starts delivering. We have this type of setup on a few other customers but they are not using Novell. We do not have any issues with them. The problem occurs only with this one customer with Novell. The Novell Engineer has tried every different setting to see if it's a timeout issue. The tough part of this is... it works for a few hours and stops. Then after about 12 hours not working, it starts working again on its own or if we restart the SF service. Dan Blickensderfer |
Replies:
Posted By: LogSat
Date Posted: 11 December 2006 at 7:40pm
|
Dan, Starting from build 3.1.3.597, the timeout for the outgoing connections can be specified in the SpamFilter.ini file. The default is 60 seconds, and the value can be modified using the:   ReadTimeoutOutgoingoption. Could you zip us a few hours of SpamFilter's activity logfile for a day this happens, so we can try to spot any problems from the logs? Also, could you try changing the option: SpoolQueueFilesToMemory in the SpamFilter.ini file, and set it to 0 (zero)? This prevents a new feature in version 3.x that spools outgoing files to memory, and forces them to be spooled to disk. ------------- Roberto Franceschetti http://www.logsat.com" rel="nofollow - LogSat Software http://www.logsat.com/sfi-spam-filter.asp" rel="nofollow - Spam Filter ISP |