Trustwave and Cybereason Merge to Form Global MDR Powerhouse for Unparalleled Cybersecurity Value. Learn More

Trustwave and Cybereason Merge to Form Global MDR Powerhouse for Unparalleled Cybersecurity Value. Learn More

Services
Managed Detection & Response

Eliminate active threats with 24/7 threat detection, investigation, and response.

Co-Managed SOC (SIEM)

Maximize your SIEM investment, stop alert fatigue, and enhance your team with hybrid security operations support.

Advisory & Diagnostics

Advance your cybersecurity program and get expert guidance where you need it most.

Penetration Testing

Test your physical locations and IT infrastructure to shore up weaknesses before exploitation.

Database Security

Prevent unauthorized access and exceed compliance requirements.

Email Security

Stop email threats others miss and secure your organization against the #1 ransomware attack vector.

Digital Forensics & Incident Response

Prepare for the inevitable with 24/7 global breach response in-region and available on-site.

Firewall & Technology Management

Mitigate risk of a cyberattack with 24/7 incident and health monitoring and the latest threat intelligence.

Solutions
BY TOPIC
Microsoft Security
Unlock the full power of Microsoft Security
Offensive Security
Solutions to maximize your security ROI
Rapidly Secure New Environments
Security for rapid response situations
Securing the Cloud
Safely navigate and stay protected
Securing the IoT Landscape
Test, monitor and secure network objects
Why Trustwave
About Us
Awards and Accolades
Trustwave SpiderLabs Team
Trustwave Fusion Security Operations Platform
Trustwave Security Colony
Partners
Technology Alliance Partners
Key alliances who align and support our ecosystem of security offerings
Trustwave PartnerOne Program
Join forces with Trustwave to protect against the most advance cybersecurity threats
Loading...
Loading...

PRB: Reputation service not blocking any email

Expand / Collapse


This article applies to:

  • Trustwave MailMarshal (SEG)

Symptoms:

  • A reputation service such as Spamhaus or Marshal IP Reputation Service is not blocking anything

Causes:

If you find that you are not blocking any mail with a reputation service, then there may be a DNS issue which causes a negative result for every IP address checked, even if the IP is really listed on the Reputation Service list. The net result is that e-mail will not get blocked by the service. 

Information:

We can use NSLookup to check that your DNS server is configured to perform the RBL checks correctly. 

  1. From a command prompt, enter NSLookup
  2. Select your DNS server (not RBL server) as necessary.

    • To test against the DNS server used by MailMarshal, enter the DNS IP listed in the Configurator under Tools | Server Properties | Delivery.


      >
      server 10.12.2.12
      Default Server:  dns1.mydomain.corp
      Address:  10.12.2.12
      >

    • Set type to "any":
      >set type=any
    • Select IP address to check. The address 127.0.0.2 is generally listed on RBL lists for testing. 
    • Determine a reputation service domain, such as sbl.spamhaus.org or bl.spamcop.net.
    • Reverse the IP address and join it with the reputation service domain as in the example below:


      127.0.0.2 with bl.spamcop.net becomes:
      2.0.0.127.bl.spamcop.net


      This give a positive result of:

      >2.0.0.127.bl.spamcop.net
      Server:  dns1.mydomain.corp
      Address:  10.12.2.12

      Non-authoritative answer:
      2.0.0.127.bl.spamcop.net        internet address = 127.0.0.2
      2.0.0.127.bl.spamcop.net        text =  "Blocked - see
      http://www.spamcop.net/bl.shtml?127.0.0.2"


      A positive result from SpamHaus looks like this:


      > 2.0.0.127.sbl.spamhaus.org
      Server:  dns1.mydomain.corp
      Address:  10.12.2.12

      Non-authoritative answer:
      2.0.0.127.sbl.spamhaus.org      internet address = 127.0.0.2
      2.0.0.127.sbl.spamhaus.org      text = "
      http://www.spamhaus.org/SBL/sbl.lasso?query=SBL233
      "


      A negative result should occur if testing 127.0.0.1 (instead of 127.0.0.2).


      > 1.0.0.127.sbl.spamhaus.org
      Server:  dns1.mydomain.corp
      Address:  10.12.2.12

      *** dns1.mydomain.corp can't find 1.0.0.127.sbl.spamhaus.org: Non-existent
      domain
      >

If you do not get the positive result for 127.0.0.2 and a negative result for 127.0.0.1, then your DNS is not configured to handle the RBL checks correctly. Either correct the issue in your DNS server, or use an alternative DNS server which passes the above tests. Note that some ISPs deliberately block DNS requests to RBL lists to reduce the extra load on their servers.

Troubleshooting your DNS server setup is beyond the scope of Trustwave Support.

This article was previously published as:
NETIQKB39092

 

 


To contact Trustwave about this article or to request support:


Rate this Article:
     
Tags:

Add Your Comments


Comment submission is disabled for anonymous users.
Please send feedback to Trustwave Technical Support or the Webmaster
.