Skip to main content

LevelBlue Completes Acquisition of Cybereason.  Learn More

LevelBlue Completes Acquisition of Cybereason.  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 Security
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
LevelBlue Security Operations Platforms
Security Colony
Partners
Microsoft Security
Unlock the full power of Microsoft Security
Technology Alliance Partners
Key alliances who align and support our ecosystem of security offerings
Loading...
Loading...

INFO: Message Release with MailMarshal SES

Expand / Collapse


This article applies to:

  • MailMarshal SES
  • MailMarshal (SEG)

Question:

  • What are the special issues when using Automatic Message Release with MailMarshal SES?

Information:

MailMarshal SES provides the same Message Release external command functionality that is available in MailMarshal SMTP. For basic information, see the MailMarshal SES User Guide (Chapeter 8, "External Commands").

When you use this functionality in MailMarshal SES, be aware of the following considerations:

  1. Use the variable {ReleaseProcessRemaining} in your notifications. This ensures that any released messages pass through all rules. Processing all rules is particularly important with MailMarshal SES, to correctly apply encryption and decryption.
  2. If you use MailMarshal SES as a plug-in to MailMarshal SMTP, you must configure rules in MailMarshal SMTP to forward release requests to MailMarshal SES.
    • Note that if you use Message Release in both products, you must set up a different notification "from" address in the quarantine rule of each product, and modify the message release processing rule to use the correct address.
    • For instance if you use the default MessageRelease@release.it in MailMarshal SMTP, you could use SESMessageRelease@release.it in MailMarshal SES.

Notes:

As always, it is good practice to test your rules before putting them into production.


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
.