XADM: Autoforward Rules May Be Disabled When Using Antivirus API

When a mailbox that contains an autoforward rule attempts to process the rule, if a message contains an attachment and the server uses a program that is based on the antivirus application programming interface (API), the information store may disable the autoforward rule.

The client receives a "Rule In Error" error message that lists the name of the rule with the reason "Unknown Error."

This issue can occur because the antivirus API scans any attachments.

If the information store does not detect this condition when the attachment is being scanned, the information store disables the rule.

To resolve this problem, obtain the latest service pack for Exchange Server 5.5. For additional information, click the following article number to view the article in the Microsoft Knowledge Base: NOTE: When you start this version of the information store, the information store databases are automatically upgraded to a new format. After the databases have been upgraded, you can restore an earlier version of the Store.exe file on the server, but only if it is version 5.5.2652.68 or later. If you restore a Store.exe file earlier than version 5.5.2652.68 after the database has been upgraded, you are no longer able to start the information store. For additional information, click the article number below to view the article in the Microsoft Knowledge Base: The following files are available for download from the Microsoft Download Center:
For additional information about how to download Microsoft Support files, click the following article number to view the article in the Microsoft Knowledge Base: Microsoft scanned this file for viruses. Microsoft used the most current virus-detection software that was available on the date that the file was posted. The file is stored on security-enhanced servers that help to prevent any unauthorized changes to the file.

Microsoft has confirmed that this is a problem in Microsoft Exchange Server version 5.5 Service Pack 3. This problem was first corrected in Exchange Server 5.5 Service Pack 4.

After this fix is applied, the information store properly detects this condition and waits the amount of time that is specified in the OpenRetryDelay registry key.