You can use this hotfix to force Exchange 2000 to emulate
the Exchange Server 5.5 message deletion logic. To do so, use ADSI Edit or
Ldp.exe to edit the
msExchMailboxManagerAgeLimit attribute on the Mailbox Manager recipient policy
object.
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 Windows Server 2003, Microsoft Exchange 2000 Server, Microsoft Exchange Server 2003, or both Windows and Exchange. 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.
How to set one of the following values on the msExchMailboxManagerAgeLimit attribute
You can find the msExchMailboxManagerAgeLimit attribute by opening the configuration container in adsiedit.msc and getting properties on the relative mailbox manager policy object:
CN=%name_of_policy%,CN=Recipient Policies,CN=%orgname%,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=tree,DC=exchadmin,DC=com
When you set a value of 1, you can expect the following behavior:
- We ignore the modified date property on messages and delete messages whose delivery and submitted date property exceed the age limit that is set by the policy setting.
When you set a value of 2, you can expect the following behavior:
- We ignore the submitted date property on messages and delete messages whose delivery and modified date property exceed the age limit that is set by the policy setting.
When you set a value of 3, you can expect the following behavior in Exchange 2000 Server: (Exchange 5.5 behavior)
- We ignore both the submitted and the modified date properties on messages and delete messages whose delivery date property exceeds the age limit that is set by the policy setting.
Important If you configure the behavior of Exchange
Server, programs that are built over Exchange 2000 Server and that rely on the default
behavior (which is to check all three message times before deleting the
message) may not work as expected. As with any hotfix, we recommend
that you test the hotfix thoroughly in a non-production environment before you
deploy the hotfix.