02-06-2018 07:46 AM - edited 03-08-2019 07:32 PM
I hope someone can give me a hand. We have an IronPort C170. We have an outgoing content filter set up to encrypt emails based on keywords. I read another post that states this problem can happen if the string is done incorrectly, but based on that, our appears to be correct (our rule displays as: subject=="(?i)\\[encrypt\\]"). This has just started in the last few weeks where emails that are sent out with out the trigger in the subject line are still be sent encrypted. I can't figure out why this is happening. Does anyone have any ideas? Thanks in advance.
02-06-2018 03:43 PM
Could you share the message tracking details for the email that was encrypted without this subject?
The condition appears to be correct. Ot looks for the word encrypt upper and lower cases within [].
Regards
Libin Varghese
02-08-2018 07:20 AM
Get your rule to do an additional action as well as encrypting mail; say adding a header.
There's a chance that you may find that something else is doing the encrypting.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide