Content Filtering on HTML Email
Problem reported by Loretta McDonald - November 10, 2014 at 2:05 PM
Known
I am at a loss... I think the Content Filter should be perfect for what I am trying to do, but I have tried it at least 20 different ways and it is not working.  I can only theorize the HTML is causing the filtering to have a problem.
 
Here is the situation, I am trying to look for key words in the Body when an email comes from a specific email address.  If I remove the Body portion of the rule and just use the from a specific email address, it works fine.  The email actually contains the text in the body twice:
  • On a new line with leading spaces followed by Carriage Return and line Feed
                    InfrastructurePingCheck<br>
And then a second time:
      <span style="color:#0000FF;">&lt;</span><span style="color:#A31515;">Name</span><span style="color:#0000FF;">&gt;</span>InfrastructurePingCheck<span style="color:#0000FF;">&lt;/</span><span style="color:#A31515;">Name</span><span style="color:#0000FF;">&gt;</span>
 
When I try any of the following, none of it seems to work.  :
  • Body without Wildcards: InfrastructurePingCheck
  • Body with Wildcard: *InfrastructurePingCheck*
  • Body with Wildcard: ?InfrastructurePingCheck?
  • Body without Wildcards: InfrastructurePingCheck<br>
  • Body without Wildcards: <span style="color:#0000FF;">&lt;</span><span style="color:#A31515;">Name</span><span style="color:#0000FF;">&gt;</span>InfrastructurePingCheck<span style="color:#0000FF;">&lt;/</span><span style="color:#A31515;">Name</span><span style="color:#0000FF;">&gt;</span>
  • Anywhere in Message without Wildcards: InfrastructurePingCheck
  • Anywhere in Message with Wildcard: *InfrastructurePingCheck*
I have checked Spam filters and junk mail and like I said earlier, it works fine without the Body portion of the rule.
 
Does anyone have any suggestions for me?

2 Replies

Reply to Thread
2
Employee Replied
Employee Post
Hello Loretta,
 
Thanks for the details. Since we have discussed this further in a Support Ticket we have confirmed the base-64 encoding is not currently supported and thus we only look for the Raw text format in emails. We have applied this to our list of features and will potentially be considered for one of our future SmarterMail releases.
 
Thanks.
 
0
Steve Reid Replied
This is clearly a bug and not a feature request.

Reply to Thread