Server Blacklist not showing all RBLs configured on the server
Problem reported by David Sovereen - January 2 at 9:13 PM
Being Fixed
When viewing the Server Blacklist it is only showing a few of the RBLs that we have configured on the server (7 in total). However, when we view Settings > Antispam > RBLs we have 28 configured. It also appears as if every IP address configured on the server is not being checked. We have also noticed that when doing a  manual review of the BlacklistAwareResults.xml file that some IP addresses that were checked will return a different number of results than others. If each IP address configured on the server is checked against the same number of RBLs this should not be the case. We are on SmarterMail 16.3.6897.

3 Replies

Reply to Thread
0
Robert Emmett Replied
Employee Post
David, the server blacklist does not pull from the RBLs configured within SmarterMail web interface.  In the Service folder (i.e., C:\Program Files (x86)\SmarterTools\SmarterMail\Service) should be a file called BlacklistAwareConfig.xml.  Unfortunately, to add or to remove from this list is a manual operation in SM16.  This file contains the RBLs against which your server will test for blacklisting.  You can copy from the spamConfig.xml file any additional RBLs.  Look from any tags with <SpamIp4rLookup> and copy those into BlacklistAwareConfig.xml.  Rename the tag to <SpamIp4rLookups>.  In a future release of SmarterMail, we allow the server blacklist to be configurable from within the interface.
Robert Emmett
Software Developer
SmarterTools Inc.
(877) 357-6278
www.smartertools.com
0
David Sovereen Replied
Hi Robert,

When I look in the BlacklistAwareConfig.xml file on the server it contains 16 RBLs, but in the Server Blacklist > Blocks by RBL list in the web interface it only shows 7 of them. For example we have the following in the BlacklistAwareConfig.xml file (all the truncated information is the same for these other than the <description>, <weight>, and the <requiredIP> values -

<SpamIp4rLookups>
    <name>SORBS - Abuse</name>
    <domainLookup>dnsbl.sorbs.net</domainLookup>
    ...
  </SpamIp4rLookups>
  <SpamIp4rLookups>
    <name>SORBS - Dynamic IP</name>
    <domainLookup>dnsbl.sorbs.net</domainLookup>
    ...
  </SpamIp4rLookups>
  <SpamIp4rLookups>
    <name>SORBS - Proxy</name>
    <domainLookup>dnsbl.sorbs.net</domainLookup>
    ...
  </SpamIp4rLookups>

However, on the web interface we only see SORBS - Abuse listed. This is the same with other RBLs that are missing in the web interface. Is this due to the fact that the missing RBLs share the same <domainLookup> value in the BlacklistAwareConfig.xml file on the server causing only the first to show up in the list on the web interface?
0
Robert Emmett Replied
Employee Post
David, you are correct that SM16 and prior were only limiting the lookups based on the domainLookup value.  So if you had more SORBS entries, it would actually only check the first entry.  This has been fixed and will be available in the next public release of SM16.  If you would like, I can send your a link to a custom build with the fix.
Robert Emmett
Software Developer
SmarterTools Inc.
(877) 357-6278
www.smartertools.com

Reply to Thread