Skip to main content

LevelBlue Named Official Cybersecurity Advisor of the PGA of America. Learn more

LevelBlue Named Official Cybersecurity Advisor of the PGA of America. Learn more

Services
Cyber Advisory
Managed Cloud Security
Data Security
Managed Detection & Response
Email Security
Managed Network Infrastructure Security
Exposure Management
Security Operations Platforms
Incident Readiness & Response
SpiderLabs Threat Intelligence
Solutions
BY TOPIC
Offensive Security
Solutions to maximize your security ROI
Operational Technology
End-to-end OT security
Microsoft
Unlock the full power of Microsoft Security
Securing the IoT Landscape
Test, monitor and secure network objects
Why LevelBlue
About Us
Awards and Accolades
LevelBlue SpiderLabs
PGA of America Partnership
Secure What's Next
LevelBlue Security Operations Platforms
Security Colony
Partners
Microsoft
Unlock the full power of Microsoft Security
Technology Alliance Partners
Key alliances who align and support our ecosystem of security offerings
Loading...
Loading...

PRB: Messages from other transport agents can be deadlettered

Expand / Collapse


This article applies to:

  • MailMarshal Exchange 5.3 and above
  • NOTE: Change of default behavior in version 7.1

Symptoms:

  • Messages from other transport agents can be deadlettered

Causes:

  • MailMarshal Exchange processes all mail flowing through the Hub Transport server by default, including messages that have been generated by other transport agents configured on the Hub Transport server, such as AV scanners' notifications or notifications generated by the Hub Transport Rules agent.

  • In some rare cases, messages generated by other agents can be formed in unusual ways, and MailMarshal Exchange can deadletter these messages.

Resolution:

In MailMarshal Exchange release 5.3.2 and above, you can control whether MailMarshal Exchange processes messages created by other transport agents with a Registry setting. 

Note:

  • In versions 5.3 and 7.0, all messages are processed by default.
  • In version 7.1, messages from other transport agents are NOT processed by default.

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

Version 7.X

  1. On the Array Manager server, open the Registry Editor.
  2. Navigate to the appropriate Registry location:
    • HKey_Local_Machine\Software\Wow6432Node\Marshal\MMExchange\Default\Engine
  3. Under the Engine key, create a new value with the following properties:
    • Type: DWORD
    • Name: AllowOtherFileSources
    • Data: To enable mail to bypass the MailMarshal Exchange Engine, set this value to 1. To disable the bypass, set it to 0.
    • Default (if the value is not present):
      • In version 7.0 the default is 0 (disable bypass).
      • In version 7.1 the default is 1 (enable bypass). 
  4. To apply the change, commit configuration.

Version 5.3

  1. On the affected server, open the Registry Editor.
  2. Navigate to the appropriate Registry location:
    • HKey_Local_Machine\Software\Wow6432Node\Marshal Software\MailMarshal For Exchange\Default\Engine
  3. Under the Engine key, create a new value with the following properties:
    • Type: DWORD
    • Name: AllowOtherFileSources
    • Data: To enable mail to bypass the MailMarshal Exchange Engine, set this value to 1. To disable the bypass, set it to 0.
    • Default (if the value is not present):
      • In versions 5.3  the default is 0 (disable bypass).
  4. Restart the MailMarshal Exchange Engine service.

To contact LevelBlue 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
.