XADM: News Article with Followup-To Property Defined Cannot Be Posted (260063)


The information in this article applies to:

  • Microsoft Exchange Server 5.5 SP3
This article was previously published under Q260063

SYMPTOMS

After you install a post-Exchange Server 5.5 Service Pack 3 information store fix that has a version later than version 5.5.2651.41 on a computer running Exchange Server 5.5 Service Pack 3, you cannot post a news article that has the Followup-To property defined to a newsgroup on the server. The following error message is displayed in Microsoft Outlook Express:
441 posting failed
Also, if you have a newsfeed configured on the server to accept replication from an external news server, all news articles that have the Followup-To property defined are rejected. If you enable the Network News Transfer Protocol (NNTP) log, the following error message is logged in the log file:
437 article rejected = do not try again

CAUSE

This issue can occur because the fix for another issue causes the type of the PR_INTERNET_FOLLOWUP_TO property to be processed incorrectly.

RESOLUTION

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:

191914 XGEN: How to Obtain the Latest Exchange Server 5.5 Service Pack

The following files are available for download from the Microsoft Download Center:

x86: DownloadDownload Q248838engi.exe now
Alpha: DownloadDownload Q248838enga.exe now

For additional information about how to download Microsoft Support files, click the following article number to view the article in the Microsoft Knowledge Base:

119591 How to Obtain Microsoft Support Files from Online Services

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.

STATUS

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.
Modification Type:MinorLast Reviewed:9/23/2005
Keywords:kbHotfixServer kbQFE kbbug kbExchange550preSP4fix kbExchange550sp4Fix kbfix kbgraphxlinkcritical kbQFE KB260063
©2004 Microsoft Corporation. All rights reserved.