Forefront Server Protection 2010 for Exchange: Notifications behaving differently on E2007/2010

Question

Hi all and happy holidays:
I have this particular situation with two client FSPE implementations recently.
I got one one client with a single E2007 server with FSPE v.11.0.713.0 and another one with a single E2010 server with FSPE v.11.0.713.0. I configured 'Keyword Filter Match' email notifications to Administrators and, to Internal Senders notifying them
not to use certain keywords in the future. The configuration of the notifications is exaclty the same and is using the following fields in the body of the message:
%Product% has detected a blocked keyword match on a message you sent.
      Filter Name: "%Filter%"
      State:  "%State%"
      Subject line:  "%Message%"
      Sender:  "%ISAddress%%ESAddress%"
      Recipients: "%IRAddresses%%ERAddresses%"
      Scan job:  "%ScanJob%"
      Location:  "%Company%/%Site%/%Server% (%Folder%)"
Certain kewords are not allowed through this mail system as they may be offensive to others. Please refrain from using this word(s) in the future. If you believe you received this in error, contact your system administrator.
Notifications are working great, detecting when a user is Internal Sender  and delivering the message correctly but here's the issue:
1. On the E2007 system, when the user/administrator get the notification from FSPE, the %Filter% field it displays the actual keyword that that was used:
Microsoft Forefront Protection for Exchange Server has detected a keyword filter match.
Filter name:  "English Profanity: <RealUglyWord>;English Profanity: <RealUglyWord>"
2. On the E2010 system however, when the user/administrator get the email notifications, the %Filter% field only displays the name of the keyword list:
Microsoft Forefront Protection for Exchange Server has detected a keyword filter match.
      Filter Name: "English Profanity"
No biggie you may think but, the issue is that the user has no way to know for sure which words should not use. Of course they can call the Administrator but this will cause uneeded calls to the helpdesk IMO. In the case of English profanity, it may
be obvious but, in the case of other keyword lists, it may not be so obvious. For example, I also have another keyword list blocking racist terms. To some people the word 'gringo' may be offensive, but not to others. IMO, it should not be used
at all, and I am hispanic. In any case, the user needs to know for sure which words are being blocked and not to use it IAW company policy and know that the message was not delivered. Similar keyword lists are in use on both clients for "Spam-like
language', 'Sexual harassment', etc, etc so, this is an important client requierement and part of their 'Suitable Working Envrionment' policy and enforcement.
Hope anybody has any ideas on how to fix it.
Regards,
Fred Larracuente

Answer 1

Remove filter name from the notification area