Some non-ASCII characters are not recognized by Messaging Gateway content filters
search cancel

Some non-ASCII characters are not recognized by Messaging Gateway content filters

book

Article ID: 276145

calendar_today

Updated On:

Products

Messaging Gateway

Issue/Introduction

When creating content filters, including dictionaries, you have noticed that detection is not working as expected for some words containing characters outside of the US ASCII character set. While the Control Center appears to accept these characters during rule creation, the rules do not match messages which contain the non-ASCII characters.

Example:

  • FREESPIN
  • FREESPİN
  • freespin
  • freespın

Messages using the worlds with non-ASCII characters (highlighted in red) may not be filtered as expected by the associated content rule.

Note: This only affects customer created content rules and does not affect anti-spam or malware filtering.

Resolution

This is a known limitation in the current Content Filtering implementation and may be addressed in a future Messaging Gateway release.

Powered by Wolken Software