visit-the-following

An Exchange Server 2007 Transport Rule does not work as expected

A Microsoft Exchange Server 2007 Transport Rule does not work as expected. For example, an email message that an administrator expects to be rejected may instead be delivered.
This issue can occur if the Transport Rule is based on a regular expression. For example, this issue can occur if you use the “$” character to create a pattern-matching regular expression.

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.

To work around this issue, use one of the following methods.

Method 1

Create a Transport Agent and then implement your own .NET Framework regular expressions to route email messages.

Method 2

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.

Regular expressions are a powerful, flexible way to evaluate a character sequence for matching against a given series of characters. Typically, a regular expression is written in a programming language such as C++ or C#. The regular expression can then be interpreted by a regular expression processor. The processor examines the character sequence and identifies parts that match the provided characters.

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 more information about Transport Agents in Exchange Server 2010, visit the following TechNet website:
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:

Continue Reading:
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

Consider the following scenario:  
  • 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.

This issue occurs because the UM auto attendant does not specify the value of the interdigittimeout attribute when it loads the menu. Therefore, the default value of the interdigittimeout attribute of 1 second is used.
To resolve this issue, install the following update rollup:
2509911 

(http://support.microsoft.com/kb/2509911/
)
Description of Update Rollup 4 for Exchange Server 2007 Service Pack 3

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the “Applies to” section.
For more information about UM auto attendants, visit the following Microsoft website:For more information about how to create a new UM auto attendant, visit the following Microsoft website:For more information about how to enable or disable directory lookups for a UM auto attendant, visit the following Microsoft website:For more information about the interdigittimeout attribute, visit the following Microsoft website:

Taken from:
A UM auto attendant times out and generates an invalid extension number error message in an Exchange Server 2007 environment

Recent Comments

    Archives

    Categories