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
|