Print Page | Close Window

Server too busy

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=6198
Printed Date: 11 July 2025 at 9:22am


Topic: Server too busy
Posted By: Hyldsgaard
Subject: Server too busy
Date Posted: 14 August 2007 at 6:13am
Hi there!

I think I’ve found an error in Spamfilter.

When Spamfilter tries to forward an email to the end mail server and that mail server is too busy, Spamfilter simply doesn’t register that there was an error and just thinks that it has forwarded the email correctly.

Below you can see the logfile for one of these instances.

After this there is nothing in the Spamfilter queue and Spamfilter never tries to deliver the message again. On the receiving mail server all I’ve got is the communication with Spamfilter where it tells the filter, that it’s too busy.

Am I missing some sort of setting in Spamfilter or is this an error? I’m using Spamfilter .705.

08-14-07 09:42:09:614 -- (7756) Connection from: 62.243.4.39 - Originating country : Denmark
08-14-07 09:42:10:052 -- (7756) - SPF analysis for sparekassenfaaborg.dk done: - none
08-14-07 09:42:10:052 -- (7756) Mail from: mlp@sparekassenfaaborg.dk
08-14-07 09:42:15:083 -- (7756) DNS Error:TimedOut
08-14-07 09:42:15:255 -- (7756) RCPT TO: mhn@boligfyn.dk accepted
08-14-07 09:42:15:255 -- (7756) - MAPS search done...
08-14-07 09:42:15:770 -- (7756) Warning - Message exceeds MaxMsgSizeForKeywordScan, skipping statistical scan
08-14-07 09:42:15:770 -- (7756) EMail from mlp@sparekassenfaaborg.dk to mhn@boligfyn.dk passes Bayesian filter - 0% spam (0ms)
08-14-07 09:42:15:770 -- (7756) Checking SURBL
08-14-07 09:42:15:770 -- (7756) Starting queueing procedures
08-14-07 09:42:15:786 -- (7756) EMail from mlp@sparekassenfaaborg.dk to mhn@boligfyn.dk was queued. Size: 707 KB, 723968 bytes

08-14-07 09:42:15:802 -- (8144) Sending email from mlp@sparekassenfaaborg.dk to mhn@boligfyn.dk --
08-14-07 09:42:15:927 -- (8144) EMail from: mlp@sparekassenfaaborg.dk to: mhn@boligfyn.dk -- was returned to sender - server error - mail.jirty.dk said: Sorry, SMTP server too busy right now (50); try again later --
08-14-07 09:42:16:364 -- (8144) Error-email from mlp@sparekassenfaaborg.dk to mhn@boligfyn.dk -- was forwarded to mail.jirty.dk
08-14-07 09:42:16:364 -- (8144) Exception occurred during TSendMailThread.SendErrMsg: Sorry, SMTP server too busy right now (50); try again later --
08-14-07 09:42:16:364 -- (8144) server error - mail.jirty.dk said: Sorry, SMTP server too busy right now (50); try again later --


Replies:
Posted By: LogSat
Date Posted: 14 August 2007 at 7:28am
I'm not sure this is an error. It really depends on the error code that your server sent along with the "server busy" error.

If the error code is in the 400 range (4xx), then the RFC states that the error condition is temporary, and the action should be attempted again.

If the error code is in the 500 range (5xx), then per RFC this is a permanent error, and the SMTP client (SpamFilter in this case) should be discouraged from trying again.

This said, SpamFilter has to options in the SpamFilter.ini file that can override the default behavior in these two cases:

;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

Going back to the possible bug, if you have the above default values in SpamFilter, and your server rejected the email with an error similar to:

450 Sorry, SMTP server too busy right now (50); try again later

then yes, that should be a bug and we'll need to look at it in more detail. If instead your server rejected the email with an error like:

550 Sorry, SMTP server too busy right now (50); try again later

Then that is by design and is how things should work per RFC (but which you can override if you wish by changing the two options above).







-------------
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