Because there may be several causes of this problem, use one or more of the following resolutions as appropriate for your situation.
Resolution 1
The Norton Symantec AntiVirus Corporate Edition 9.x Internet E-mail Auto-Protect scanner feature should not be enabled. To remove this feature, follow the steps that are described in Symantec document ID 2004061009504348. To view this document, visit the following Symantec Web site:
Resolution 2
E-mail systems such as Microsoft Exchange Server 5.5 do not recognize STNEF formatting. If you have to work with such e-mail systems, you must force the store driver in Exchange Server 2003 to use Transport Neutral Encapsulation Format (TNEF). To do this, you must configure several registry entries on the Exchange Server 2003 server.
For more information about how to do this, click the following article number to view the article in the Microsoft Knowledge Base:
254089
Required registry setting when using SMTP connector as a site connector to Exchange Server 5.5
Resolution 3
You must disable heuristics scanning in the Symantec Mail Security for Microsoft Exchange program. To do this, refer to the program's Help files. Alternatively, contact Symantec for help.
Resolution 4
To verify this cause, you can telnet to the remote server. For example, to telnet to a server that is named
server.domain.com, follow these steps:
- Open a command prompt.
- At the command prompt, type telnet server.domain.com 25, and then press ENTER.
You must receive a response that resembles the following:
220 hostname.domain.com Microsoft ESMTP MAIL Service, Version: 5.0.2195.1600 ready at Thu, 30 Nov 2000 18:09:43 -0600
If you do not receive a similar response, edit the metabase to configure an SMTP banner.
For more information, click the following article number to view the article in the Microsoft Knowledge Base:
281224
How to modify the SMTP banner
Resolution 5
Disable the
IP INSPECT NAME Inspection_Name SMTP statement on the Cisco firewall. For more information about how to do this, refer to the product's manual. Alternatively, contact Cisco for help.
Resolution 6
If the other causes do not apply, the metabase may be corrupted. To replace a corrupted metabase, follow the steps in the "The IIS metabase is corrupted" section of the following article in the Microsoft Knowledge Base:
304166 Exchange databases are not mounted and event logs contain error messages