Bug Report
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=6492
Printed Date: 22 December 2025 at 1:13pm
Topic: Bug Report
Posted By: kspare
Subject: Bug Report
Date Posted: 02 June 2008 at 10:43am
|
Over the weekend the drive out smtp connector for exchange sits on ran out of space. this morning while checking the logs for logsat we noticed that when it tried to send the message through to our server it would report the server as being out of space and drop the message. 4.3.1 Out of memory But the logsat server doesn't say what it does with the message. I assume it dropped. but is there a ndr sent out? Can we have the option to cache the emails instead of dropping them. IMHO out of memory is no different than just being down and we should be cacheing email for our own servers let alone customer servers that many people supply relaying services for. can this be fixed roberto? |
Replies:
Posted By: Desperado
Date Posted: 02 June 2008 at 12:57pm
|
Kevin,
Unless I mis-understand your issue, if the following setting is set, it should queue for later delivery.
QueueIfDestinationError400=1
Also, the number of hours it will attempt delivery for depends on the setting
ExpireRetryQueueHours=hh ------------- The Desperado Dan Seligmann. Work: http://www.mags.net Personal: http://www.desperado.com |
Posted By: kspare
Date Posted: 02 June 2008 at 1:30pm
When was that feature added? I never knew about it 
|
Posted By: LogSat
Date Posted: 02 June 2008 at 10:52pm
|
SpamFilter will queue emails if the destination SMTP server is not available or is not responding to connection requests, and will retry delivery every few minutes until the server is back online. If the destination server is available and is responding to SMTP traffic, but rejects emails due to errors, then this error conditions should result in Exchange erroring out connection requests with SMTP error codes. These error codes can be in the 400-499 range, indicating a temporary error condition, or in the 500-599 range, indicating a more permanent condition. Per RFC, servers are supposed to retry delivery for a reasonable amount of time if the errors are in the 4xx range, and give up and notify the sender with a NDR (non-deliverable email report) if the errors are in the 5xx range. SpamFilter does follow this behavior by default, even though this default behavior can be changed with these two parameters in the SpamFilter.ini file: ;Determines if SpamFilter should hold in the queue emails that were rejected by the destination SMTP server with an error in the 4xy range QueueIfDestinationError400=true ;Determines if SpamFilter should hold in the queue emails that were rejected by the destination SMTP server with an error in the 5xy range QueueIfDestinationError500=false What actually happened thus depends on how your Exchange server was rejecting emails that SpamFilter was forwarding to it. If you send us a few minutes worth of SpamFilter’s activity logfile when Exchange was down we’ll try to find out more. ------------- Roberto Franceschetti http://www.logsat.com" rel="nofollow - LogSat Software http://www.logsat.com/sfi-spam-filter.asp" rel="nofollow - Spam Filter ISP |