Note Microsoft Exchange Server 2007 and Microsoft Exchange Server 2010 do not implement the full Microsoft .NET Framework regular expression classes. Additionally, the intermediate language that is generated may be incorrect.
Create a Transport Agent and then implement your own .NET Framework regular expressions to route email messages.
Use a filter to automatically process email messages. For example, use Microsoft ForeFront Security for Exchange Server to filter email messages based on the email originator and email recipient.
You can create a Transport Rule based on regular expressions in the Exchange Management Shell (EMS) by using the New-TransportRule cmdlet. When you use the Conditions parameter, the Exchange regular expression implementation is used. You can use regular expressions in any predicate that accepts the “Patterns” predicate property.
Transport Rule conditions and exceptions consist of one or more predicates. Predicates instruct the Transport Rules agent on a Hub Transport server (or the Edge Rules agent on an Edge Transport server) to examine a specific part of an email message. Those specific parts include sender, recipients, subject, other message headers, and message body. Then, the Transport Rule determines whether the rule should be applied to that message. Therefore, predicates act as building blocks for conditions and exceptions.
In the Exchange Management Console, you can use regular expressions with any condition or exception that contains the words “text patterns.” For example, you can use regular expressions with the following condition:
“when the From address contains text patterns”
Note The “Patterns” predicate accepts a regular expression that can be used to match text that follows an identifiable pattern. You must enclose the expression in quotation marks (“).
For information about how to use the NewTransportRule cmdlet, visit the following TechNet website:
For information about regular expressions and how to use regular expressions in Exchange Server 2007 Transport Rules, visit the following TechNet website:
For information about how to use predicates to create conditions and exceptions in an Exchange Server 2010 Transport Rule, visit the following TechNet website:
An Exchange Server 2007 Transport Rule does not work as expected
A UM auto attendant times out and generates an invalid extension number error message in an Exchange Server 2007 environment
- You create a Unified Messaging (UM) auto attendant on a Microsoft Exchange Server 2007 UM server.
- You configure the UM auto attendant to only accept dual tone multi-frequency (DTMF) inputs.
- You disable directory lookups for the UM auto attendant.
- You make a call that is answered by the UM auto attendant asking for the extension number.
- You type the extension number.
In this scenario, the UM auto attendant times out unexpectedly. Additionally, an invalid extension number error message is generated.
Note This issue does not occur when you type each digit within 1 second.
Description of Update Rollup 4 for Exchange Server 2007 Service Pack 3