Can anti-spam custom rules that use "Body" as the source read base64 encoded text?
Question asked by A System Administrator - 3/10/2022 at 11:38 AM
Hi all,

I've been getting more and more scam/phishing messages that are sending text as base64 encoded strings so my filters that use "raw content" are not effective. In the message that's shown in the inbox the text is decoded so I thought maybe the "body" source on a custom rule would work but it does not seem to be.

Can someone from SmarterTools confirm/deny if any of the spam check custom rule sources can match against base64 encoded text? If they currently do not, can they be made to? Base64 encoding a string is an easy way to totally bypass any custom filters otherwise.


Reply to Thread