Forum Discussion
Block outbound RMS Encrypted Emails with Exchange Transport Rule?
- Dec 01, 2017
Circling back on this - we worked with MSFT Support and they confirmed it no longer works using rpmsg.message.
They work-around they provided, which we confirmed works, is checking for a message type that is "Permission Controlled"
Funny, customers usually care about the opposite scenario :)
I believe the "encrypted" option for message type refers to S/MIME, for RMS/AIP protected messages try creating a rule that looks the following header - Content-Class: rpmsg.message
Or the "msip_labels" header, but that's only added when manually labeling the email I suppose.
- Joe StockerNov 03, 2017Bronze Contributor
It does not seem to be blocking it. Does this rule look right to you? If so, shouldn't the rule take effect in ~15 minutes? It has been 45 minutes.
- VasilMichevNov 03, 2017MVP
You probably have to "sanitize" it, as the . symbol has special meaning when using regex ("matches"). Or just try the "header includes words" condition.
- Joe StockerNov 03, 2017Bronze Contributor
Tried using 'header includes words' to avoid the regex and it still is not blocking the emails.
I verified that on the receiving end, there is a message header called Content-Class that contains the value rpmsg.message so not sure why the rule is not working.