Incorrect handling of 4.x.x errors? |
Post Reply 
|
| Author | |
roaridse 
Newbie 
Joined: 16 February 2009 Location: Norway Status: Offline Points: 14 |
 Post Options
 Thanks(0)
 Quote Reply
 Topic: Incorrect handling of 4.x.x errors?Posted: 26 March 2012 at 3:22am |
|
We recently had a little downtime on our exchangeserver due to upgrade from 2007 to 2010 .
The mails seems to queue fine in spamfilter, but I think the handling of 4.x.x errors are incorrect?
This cannot be the the correct way to handle 4.x.x messages? |
|
 |
|
|
LogSat
Admin Group 
Joined: 25 January 2005 Location: United States Status: Offline Points: 4104 |
Post Options
Thanks(0)
Quote Reply
Posted: 26 March 2012 at 9:19pm |
|
roaridse,
You are correct - 4xx errors are temporary, and by default SpamFilter should queue until the destination SMTP server accepts them. 5xx errors are instead permanent, and SpamFilter should not queue those and return an error right away. These parameters in the SpamFilter.ini file can be used to alter this behavior: ;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 ;Determines if SpamFilter should remove from the queue emails that could not be delivered to the destination SMTP server due to a "Read Timeout" (an NDR is sent if the email is removed from the queue) DoNotQueueIfReadTimeout=false Could you please check your SpamFilter.ini file and see if the "QueueIfDestinationError400" value is set to "true" or "1"?
|
|
|
|
|
roaridse
Newbie
Joined: 16 February 2009 Location: Norway Status: Offline Points: 14 |
Post Options
Thanks(0)
Quote Reply
Posted: 27 March 2012 at 2:39am |
|
Hi,
Thanks - QueueIfDestinationError400 was set to "0" .. Explains it all.. Roar
|
|
|
|
|
LogSat
Admin Group
Joined: 25 January 2005 Location: United States Status: Offline Points: 4104 |
Post Options
Thanks(0)
Quote Reply
Posted: 27 March 2012 at 7:47pm |
|
Hi Roar,
We looked into this a bit further, and unfortunately have just discovered a bug related to the option above. We'll be fixing it in the next beta version of SpamFilter. The release note relative to this is: {TODO -cFix : If the SpamFilter.ini option DoNotQueueIfReadTimeout was set to false, it was also affecting the option QueueIfDestinationError400 by overriding it and setting it to false as well} |
|
|
|
Topic Options|
Post Reply
|
|
Tweet
|
| Forum Jump | Forum Permissions You cannot post new topics in this forum You cannot reply to topics in this forum You cannot delete your posts in this forum You cannot edit your posts in this forum You cannot create polls in this forum You cannot vote in polls in this forum |
This page was generated in 0.375 seconds.