Spam Filter ISP Support Forum

  New Posts New Posts RSS Feed - Sending wrong error response for SURBL ma
  FAQ FAQ  Forum Search   Register Register  Login Login

Sending wrong error response for SURBL ma

 Post Reply Post Reply
Author
sgeorge View Drop Down
Senior Member
Senior Member


Joined: 23 August 2005
Status: Offline
Points: 178
Post Options Post Options   Thanks (0) Thanks(0)   Quote sgeorge Quote  Post ReplyReply Direct Link To This Post Topic: Sending wrong error response for SURBL ma
    Posted: 23 May 2007 at 2:08pm
Just noticed that when a message is blocked for a SURBL match, the error response returned is actually that which I have set for my MAPS response.

I just upgraded to v6.5.3.674:SFI, but after reviewing my logs from last week, I notice that the same thing was happening on the older build I was using (v3.1.3.615).

The most likely cause of this would be that I put the wrong response in SpamFilter.ini's ResponseBlacklistedSURBL= parameter, but I checked it, and even deleted the existing param/value line to have it restore to the default.  Now, the GUI confirms that the default SURBL response is currently:

521 A URL in the email is Blacklisted by SURBL: %MAPSResponse%.

And my MAPS response in SpamFilter.ini has been:

(Sorry if this wraps... it is all one long line...)
-----
ResponseBlacklistedMAPS=521 The IP %IP% is Blacklisted by %MAPSResponse%.     Additional Info: Another email user from your domain sent out a lot of spam recently.  As a result, users such as yourself are finding that many of their outgoing messages are being rejected; many email domains use the blacklist at %MAPSResponse% to decide which IPs NOT to receive email from.  Your domain's IP (%IP%) appears on that blacklist.  You should notify your System Administrator.  If your email service is a large provider (such as Gmail or Yahoo), then they probably already know about this problem.     *** WHAT TO DO ***: Re-send your message in a few hours.  Otherwise, you can try sending your message from another email address.  For more information, see
-----


However, I still give this error response for SUBRL matches:
05/23/07 14:01:02:436 -- (4544) SURBL: surbl-org-permanent-test-point.com - 521 The IP surbl-org-permanent-test-point.com is Blacklisted by multi.surbl.org.     Additional Info: Another email user from your domain sent out a lot of spam recently.  As a result

Any help on how to get my SURBL matches to send SURBL errors would be much appreciated.  Thanks as always.

Stephen
Back to Top
LogSat View Drop Down
Admin Group
Admin Group
Avatar

Joined: 25 January 2005
Location: United States
Status: Offline
Points: 4106
Post Options Post Options   Thanks (0) Thanks(0)   Quote LogSat Quote  Post ReplyReply Direct Link To This Post Posted: 23 May 2007 at 4:49pm
Ok, we were indeed able to reproduce this. Very, very weird...
But even though we don't know the "why", we know the "what".

....bug.

Will update the posting in a few hours with the fix information.
Roberto Franceschetti

LogSat Software

Spam Filter ISP
Back to Top
LogSat View Drop Down
Admin Group
Admin Group
Avatar

Joined: 25 January 2005
Location: United States
Status: Offline
Points: 4106
Post Options Post Options   Thanks (0) Thanks(0)   Quote LogSat Quote  Post ReplyReply Direct Link To This Post Posted: 23 May 2007 at 10:19pm
Thanks for this report. We have identified the insect. It was an "errorus programmarius" which will be eliminated in the next build that will be released within the next 12/24 hours.
Roberto Franceschetti

LogSat Software

Spam Filter ISP
Back to Top
sgeorge View Drop Down
Senior Member
Senior Member


Joined: 23 August 2005
Status: Offline
Points: 178
Post Options Post Options   Thanks (0) Thanks(0)   Quote sgeorge Quote  Post ReplyReply Direct Link To This Post Posted: 24 May 2007 at 9:27am
"errorus programmarius"!  Hehe, sounds like it belongs in a Road Runner and Wile E. Coyote cartoon.  

Wow, thanks for the fix!!! 

Stephen
Back to Top
 Post Reply Post Reply
  Share Topic   

Forum Jump Forum Permissions View Drop Down



This page was generated in 0.181 seconds.