Exclamation mark is not added to email subject

[Densha Otoko]

I have issue on incoming content filter. There are 3 condition will rule only if all condition match and the action will be adding ! in the subject

Condition 1 : Envelop Sender does not contain ###.###

Condition 2 : Subject header does not contain ##

Condition 3 : URL Reputation - Matching condition custom range -10.0 to 10.0 and Check URLs within All (Message Body, Subject and Attachments)

Action : Add/Edit Header - Prepend to the value of Existing Header : [!]

The issue here is I noticed if I delete URL Reputation condition , this filter is working.

Please help to advise how can I include all the conditions and making this filter working or I must not include the URL Reputation condition

[Ken Stieers]

Try escaping it like you would for regex.

\!

[Densha Otoko]

This is my current setting.

May I know which part should I  add \!

[Ken Stieers]

My thought was that in your Add/Edit Header, you needed to change the [!] to [\!] because the regex that's prepending was treating that ! as an instruction, not a literal string to apply.
But that's not the issue... it's that you're not matching the filter...

Yes, the Japanese font might be the issue... but we'd have to test that...

[Dustin Anderson]

If I'm understanding correctly the issue isn't the ! being added, it's the URL filter? Without it it does add the !?

Just to verify you have URL filtering enabled and it's connected? (Found under Security Services -> URL Filtering)

[Densha Otoko]

This is my current setting for URL Filtering

Im still not able to hit the rule when the URL Reputation condition added to the rule

[Densha Otoko]

Hi All

Sorry I just noticed that in my message body there is no URL at all hence the rule wat not hit.

For that issue it considered solved however what about if the url already in the message body but still not hitting the rule. And the email came in Japanese font . Any possibility reason that led to this issue

[Dustin Anderson]

There is no real way to know for sure, first would be to look at the logs to see if it even detected a URL or not. It could also be one of the other 2 conditions did not match.