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.

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?

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.