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...

HOWTO: Setting behavior for Receiver rule "is not a fully qualified domain name"

Expand / Collapse


This article applies to:

  • Trustwave MailMarshal (SEG) 6.4.5 and above

Question:

  • How can I adjust the behavior of MailMarshal SMTP Receiver checking "Where sender's name is/is not a fully qualified domain name"?

Procedure:

The MailMarshal SMTP Receiver rule condition "Where sender's name is/is not a fully qualified domain name" allows you to take action based on the server name that a remote server provides as part of the HELO SMTP command.

By default this condition has the following settings:

  • Minimum 3 domain parts
  • Maximum 10 domain parts

For instance, the following are not valid FQDNs by default:

  • mailserver
  • mailserver.com
  • mailserver.some.very.long.set.of.sub.domains.at.an.ISP.somewhere.com

To configure these settings:

  1. On the Array Manager, edit the Registry (10.X: use Advanced Settings in the Management Console)
  2. Navigate to the SEG Receiver key:
    • In version 8.X: HKEY_LOCAL_MACHINE\SOFTWARE\Trustwave\Secure Email Gateway\Default\Receiver
    • 10.X: value names have the prefix Receiver. (Receiver dot).
    • For full details of the location for each product version, see article Q10832.
  3. Enter one or more of the following DWORD values:
    • HELOCheckMinSubDomains: The minimum number of domain parts required. 
    • HELOCheckMaxSubDomains: The maximum number of domain parts allowed. 
  4. Commit configuration changes
  5. Restart the Receiver service on each email processing server

Warning: Using the Registry Editor incorrectly can cause serious problems that may require you to reinstall your operating system. Trustwave cannot guarantee that problems resulting from the incorrect use of Registry Editor can be solved. Make sure that you back up your Registry prior to making any changes.

Notes:

  • The default maximum for earlier MailMarshal 6.4 releases was 5 domain parts.
  • Some well known ISPs such as Yahoo (and regional ISPs affiliated with Yahoo) use FQDNs with at least 6 parts.

To contact Trustwave about this article or to request support:


Rate this Article:
     

Add Your Comments


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