XIMS: Using Wildcards When Filtering Chat Rooms for Profanity (239660)
The information in this article applies to:
- Microsoft Exchange 2000 Server
This article was previously published under Q239660 SYMPTOMS
When you use wildcards to filter chat rooms for profanity, you may find words that you intended to be blocked are still being posted. For example, if you filter wildcard expressions such as "j?se", the filter does not match "j2se".
Also, if you define a string that includes "l[^iu]mp", the profanity filter does not match to "l + every character except i and u + mp". The profanity filter takes that string and treats it as a literal match.
CAUSE
The chat profanity filter only matches against the asterisk (*) and question mark (?) wildcard expressions. When you use the "?", the query does not match "?" to numbers, punctuation (or any other non-alphabetic printable characters). The "*" query, however, does match against alphabetic characters, numeric, and other printable characters.
RESOLUTION
To make specific word matches, you must define these words using only the "*" or "?" wildcard expressions as appropriate for the characters that you are trying to filter.
STATUSMicrosoft has confirmed that this is a problem in Microsoft Exchange 2000 Server. MORE INFORMATION
The profanity filter takes an administrator-defined string that uses specific wildcards and treats it as a literal match. Words that do not match the literal or actual string defined by the administrator are allowed to be posted. For example, the use of "l[^iu]mp" should query for a match of "l + every character except i and u + mp", but only matches against "l[^iu]mp".
| Modification Type: | Minor | Last Reviewed: | 4/25/2005 |
|---|
| Keywords: | kbbug kbpending KB239660 |
|---|
|