E-mail addresses are created incorrectly if an e-mail address policy in Exchange Server 2007 contains certain symbols, a slash or a backslash, and then another of these symbols

Article translations Article translations
Article ID: 970893 - View products that this article applies to.
Expand all | Collapse all


Consider the following scenario in Microsoft Exchange Server 2007. In Exchange Management Console, you define an e-mail address policy under E-mail Address Policies in Hub Transport under Organization Configuration. The e-mail address policy contains one of the following variables:
  • %g
  • %i
  • %s
  • %m
  • %xs
  • %xg

Immediately after one of these variables, the policy contains a slash (/) or a backlash (\). If an e-mail address policy contains another one of these variables immediately after the slash or the backslash, the e-mail address policy creates e-mail addresses that are incorrect.

Note Other variables may also cause the e-mail addresses to be created incorrectly.

For example, you may experience this issue when you use the following e-mail address policy for IBM Lotus Notes:
When you use this policy, you expect the following result:
NOTES:Joe Bloggs/JBloggs/Contoso@Exchange
However, you receive the following result:
NOTES:Joe Bloggs/%m/Contoso@Exchange


Microsoft Exchange Server 2007 does not replace symbols after the first slash, backslash or "at" sign characters in e-mail address policies. The resulting e-mail address still contains the symbols, %g, %g, %i, %s, %d, %m, %xs, and %g.


To resolve this problem, install the following update rollup:
971534 Description of Update Rollup 1 for Exchange Server 2007 Service Pack 2
After you apply this update rollup, everything before the domain separator is processed by the proxy address generator.

Note The domain separator is the final instance of the at sign (@) in the group e-mail address policy.


Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.


For more information about custom addresses, visit the following Microsoft Web site:

Exchange Server 2007 does not interpret these variables as case-sensitive. To support legacy configurations, these variables may have the percent (%) prefix or the ampersand (&) prefix.

Note In modern configurations, the percent prefix together with lowercase text is preferred.


Article ID: 970893 - Last Review: September 17, 2009 - Revision: 1.2
  • Microsoft Exchange Server 2007 Enterprise Edition
  • Microsoft Exchange Server 2007 Standard Edition
kbsurveynew kbexpertiseinter kbfix kbhotfixrollup kbqfe KB970893

Give Feedback


Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com