Article ID: 915863 - View products that this article applies to.
E-mail messages are sent from an external SMTP server through a server that is running Microsoft Exchange Server 2003 to another external messaging server that enforces Sender ID checking. However, the messages are blocked by Sender ID checking on the destination server. Messages may be transmitted from a source SMTP server though an Exchange server to a destination server in the following situations:
This problem occurs if the following conditions are true:
Apply the following hotfix to all Exchange servers in your organization. The new functionality will be augmenting PRA information on the messages that pass through the SMTP virtual server on which Content Override is enabled.
After you apply this hotfix, you must enable Content Override. To do this, run the Exarcfg.exe tool with the following command line on the Exchange servers:
exarcfg -e -s server_name -v: SMTP virtual server instance numberNote If you run this command without additional configuration, the Address Rewrite feature will not be fully enabled. For more information about how to use the Exarcfg.exe tool to turn on and to turn off the Address Rewrite feature, click the following article number to view the article in the Microsoft Knowledge Base:
904001Note Because of the performance impact that is related to the Address Rewrite feature, you should enable Content Override only on the Exchange servers that act as outgoing gateway servers.
(https://support.microsoft.com/kb/904001/ )How to use the Exarcfg.exe tool to turn on and to turn off the Address Rewrite feature in Exchange Server 2003
Hotfix informationA supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.
If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.
Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site:
http://support.microsoft.com/contactus/?ws=supportNote The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.
PrerequisitesBecause of file dependencies, this hotfix requires Microsoft Exchange Server 2003 Service Pack 2 (SP2).
Restart requirementYou do not have to restart the computer after you apply this hotfix. However, the following services are automatically restarted when you apply this hotfix:
Hotfix replacement informationThis hotfix is not replaced by any later hotfix.
File informationThe English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.
Collapse this tableExpand this table
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
Article ID: 915863 - Last Review: October 25, 2007 - Revision: 2.4