To work around this problem, use one or both of the following methods, as appropriate to your situation:
Method 1: Re-create the Exchange mailbox
- Download all the information in the mailbox to a .pst file (personal folder) by changing the delivery location in the properties for the Exchange Server service.
- Remove the corrupted mailbox by using the Exchange Server Administrator program, and then create a new Exchange Server mailbox.
- Mail from the personal folders can be uploaded to the server again by manually copying the messages back to the mailbox folders.
Method 2: Verify the Exchange homeMTA attribute
By using the Microsoft Active Directory Directory Service
To resolve this behavior by using Active Directory, perform both of the following steps:
Important
You must complete step 1 and step 2 in succession for each user who experiences this behavior.
Step 1: Verify the information that is associated with the homeMTA attribute
Use the ADSI Edit utility to obtain the information that is associated with the
homeMTA attribute of the user account that experiences this problem. To do so, follow these steps.
WARNING
: If you use the ADSI Edit snap-in, the LDP utility, or any other LDAP version 3 client, and you incorrectly modify the attributes of Active Directory objects, you can cause serious problems. These problems may require you to reinstall Microsoft Windows 2000 Server, Microsoft Exchange 2000 Server, or both. Microsoft cannot guarantee that problems that occur if you incorrectly modify Active Directory object attributes can be solved. Modify these attributes at your own risk.
- Start ADSI Edit. To do so, click Start, click Run, type adsiedit.msc in the Open box, and then click OK.
Note
The ADSI Edit tool is located in the Microsoft Windows 2000 Support Tools. If this tool is not installed, you can install the tool from the Microsoft Windows 2000 CD-ROM. The full path is: Support\Tools\Setup.exe.
- Expand
Domain NC ( servername.example.com
) (where servername
is the name of the domain controller and where example.com
is the name of the domain), expand DC= example,DC= com.
- Expand the container that contains the user account that you want; for example, expand CN=Users.
- Right-click the user account container that you want; for example, right-click CN= UserName, and then click Properties.
- In the Select which properties to view list, click Both.
- In the Select a property to view list, click homeMTA.
- In the Value(s)
box, note the value for the homeMTA
property.
If the value of the
homeMTA
attribute is not correct, you must update the user account by entering the correct value.
For example, the following is an incorrect value for the
homeMTA
attribute:
CN=Microsoft MTA\DEL:e8b60430-4dfc-4902-8891-6651a6d141c8,CN=Deleted Objects,CN=Configuration,DC=Example,DC=com;
Note
In this example, the value of the
homeMTA
attribute is in the Deleted Objects folder of the domain. In this scenario, the value of the
homeMTA
attribute must be in
CN= ServerName.
The following is an example of a correct value for the
homeMTA
attribute:
CN=Microsoft MTA,CN= ServerName,CN=Servers,CN=First Administrative Group,CN=Administrative Groups,CN=Example Organization,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=example,DC=com
To change the value of the
homeMTA
attribute:
- In the Value(s)
box, note the value for the homeMTA
property.
- Type the correct value in the Edit Attribute
box, click Set, click Apply, and then click OK.
Note
The easiest way to enter the correct value for the
homeMTA attribute
is to use ADSI Edit to obtain the correct value for a user who is in the same Exchange Server 5.5 site and who does not experience the issue that is described in the "Symptoms" section of this article. Copy the value of the
homeMTA attribute from the user who has the correct value, and then paste it in the
Edit Attribute
box of the user who has the value that is not valid.
If there are no users in the Exchange Server 5.5 site that you can copy the correct value from, use the examples that are provided earlier in this article to type the correct value manually. You must adapt the examples for your Exchange Server organization.