Sign in with Microsoft
Sign in or create an account.
Hello,
Select a different account.
You have multiple accounts
Choose the account you want to sign in with.

Symptoms

Consider the following scenario:

  • You create some recipients by using Exchange Management Console or Exchange Management Shell in a Microsoft Exchange Server 2010 or Exchange Server 2013 environment. Or, you enable some mailboxes to cloud by running the Enable-RemoteMailbox or New-MailUser cmdlet from a Microsoft Exchange Server 2013 on-premises environment.

  • The aliases of the recipients begin with one of the following combinations of lowercase characters followed by numbers or combination of numbers and letter "a" to "c":

    • sa

    • sb

    • sc

    • s

    For example, the alias is sa000c1 or s123456.

  • You create an email address policy and apply the policy to the recipients.

In this scenario, the email address policy does not generate the email addresses of the recipients correctly. For example, the secondary email address of the recipients is not generated.

Cause

This issue occurs because these aliases match a special pattern. Therefore, they are recognized as randomized proxy names incorrectly.

Resolution

To resolve this issue, install one of the following updates in your environment:

2661854 Description of Update Rollup 2 for Exchange Server 2010 Service Pack 2

3135743 Description of Cumulative Update 13 for Exchange Server 2013
After you install the update, to have us enable the update for you, go to the "Fix it for me" section. If you prefer to enable this update yourself, go to the "Let me fix it myself" section.

Fix it for me

To enable this update automatically, click the Fix it button or link. Then click Run in the File Download dialog box, and follow the steps in the Fix it wizard.




Notes

  • Install the update that is described in Microsoft Knowledge Base (KB) article 2661854 or 3135743 before you run this Fix it solution.

  • This wizard may be in English only. However, the automatic fix also works for other language versions of Windows.

  • If you are not on the computer that has the problem, save the Fix it solution to a flash drive or a CD and then run it on the computer that has the problem.


Then, go to the "Did this fix the problem?" section.



Let me fix it myself

Important
Follow the steps in this section carefully. Serious problems might occur if you modify the registry incorrectly. Before you modify it, back up the registry for restoration in case problems occur.

For Exchange Server 2010

To enable the fix after Update Rollup 2 for Exchange Server 2010 Service Pack 2 is installed, change the following registry key:

  1. Click Start, click Run, type regedit, and then press Enter.

  2. Locate the following registry key:

    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ExchangeServer\

    \Admin

  3. Right-click Admin, click New, and then click DWORD Value.

  4. Type IgnoreGeneratedProxy, and then press Enter.

  5. Right-click IgnoreGeneratedProxy, and then click Modify.

  6. In the Value data box, type 1, and then click OK.

Notes

  • If you don't see V14 or Admin registry key, you can create a new one.

  • You have to run IISreset at a command prompt and wait for 30 minutes at least after these steps.


For Exchange Server 2013

  • Before you install Cumulative Update 13 for Exchange Server 2013, following these steps:

    1. Click Start, click Run, type regedit, and then press Enter.

    2. Locate the following registry key:

      HKEY_LOCAL_MACHINE\Software\Microsoft\ExchangeServer\

      \Admin

    3. Right-click Admin, click New, and then click DWORD Value.

    4. Type IgnoreGeneratedProxy, and then press Enter.

    5. Right-click IgnoreGeneratedProxy, and then click Modify.

    6. In the Value data box, type 1, and then click OK.


    Notes

    • If you don't see the V14 or Admin registry key, create a new one.

    • You have to run IISreset at a command prompt and wait for at least 30 minutes after these steps.

  • After you install Cumulative Update 13 for Exchange Server 2013, following these steps:

    1. Click Start, click Run, type regedit, and then press Enter.

    2. Locate the following registry key:

      HKEY_LOCAL_MACHINE\Software\Microsoft\ExchangeServer\

      \Admin

    3. Right-click Admin, click New, and then click DWORD Value.

    4. Type IgnoreGeneratedProxy, and then press Enter.

    5. Right-click IgnoreGeneratedProxy, and then click Modify.

    6. In the Value data box, type 1, and then click OK.


    Notes

    • If you don't see the V15 or Admin registry key, create a new one.

    • You have to run IISreset at a command prompt and wait for at least 30 minutes after these steps.


Did this fix the problem?

  • Check whether the problem is fixed. If the problem is fixed, you are finished with this section. If the problem is not fixed, you can contact support.

  • We would appreciate your feedback. To provide feedback or to report any issues with this solution, please leave a comment on the "Fix it for me" blog or send us an email.

Workaround

To work around this issue, use uppercase characters in the aliases of the recipients. Or, manually add the email addresses of the recipients.

More Information

For more information about email address policies, visit the following Microsoft website:

General information about email address policiesFor more information about how to create email address policies, visit the following Microsoft website:

How to create email address policiesFor more information about how to apply email address policies, visit the following Microsoft website:

How to apply email address policies

Need more help?

Want more options?

Explore subscription benefits, browse training courses, learn how to secure your device, and more.

Communities help you ask and answer questions, give feedback, and hear from experts with rich knowledge.

Was this information helpful?

What affected your experience?
By pressing submit, your feedback will be used to improve Microsoft products and services. Your IT admin will be able to collect this data. Privacy Statement.

Thank you for your feedback!

×