Exchange Server 2007 may drop recipients out of the offline address book

On a server that is running Microsoft Exchange Server 2007, Exchange Server 2007 may drop recipients out of the offline address book. This problem occurs when the primary SMTP address of a recipient is changed by using the Exchange Management Console after the SMTP address is first created.

This problem occurs because the recipient's primary SMTP address was changed without updating the Mail attribute. If the Mail attribute does not match the primary SMTP address, the recipient will be dropped when the offline address book is generated.

Note You can use either the Exchange Management Shell or the Active Directory Service Interfaces (ADSI) Edit tool to modify the SMTP address and the Mail attribute. Perform this change outside the Exchange Management Console.

Service packs

Microsoft Exchange Server 2007 Service Pack 1 (SP1)

Exchange Server 2007 SP1 was released on November 29, 2007.

How to obtain the service pack

To obtain Exchange Server 2007 SP1, visit the following Microsoft Web site:

Issues that the service pack fixes

To view a list of the fixes in Exchange Server 2007 SP1, click the following article number to view the article in the Microsoft Knowledge Base:

To work around this problem, use one of the following methods:

• Use the -WindowsEmailAddress argument in addition to the -PrimarySmtpAddress argument when you change the e-mail addresses by using the Exchange Management Shell.
  
  An example of a command that uses these arguments is as follows:
  Set-Mailbox user@fabrikam.com -EmailAddressPolicyEnabled:$False -PrimarySmtpAddress ju@domain.com -WindowsEmailAddress ju@domain.com
• Use the ADSI Edit tool to manually correct the Mail attribute on the user object in the Active Directory directory service.

To locate users who are experiencing this problem, you can use the following PowerShell command: To make a bulk modification of users who are affected when their Windows e-mail address is set to their primary SMTP address, you can use the following PowerShell command:

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

This problem was first corrected in Exchange Server 2007 Service Pack 1.

For more information, click the following article numbers to view the articles in the Microsoft Knowledge Base: