Select the product you need help with
XADM: News Article with Followup-To Property Defined Cannot Be PostedArticle ID: 260063 - View products that this article applies to. 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
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.
RESOLUTIONTo 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 The following files are available for download from the Microsoft
Download Center:
(http://support.microsoft.com/kb/191914/EN-US/
)
XGEN: How to Obtain the Latest Exchange Server 5.5 Service Pack
x86:
For additional information about how to download Microsoft Support files, click the following article number to view the article in the Microsoft Knowledge Base:
Collapse this image ![]()
(http://www.microsoft.com/downloads/release.asp?ReleaseID=25443)
Alpha: Collapse this image ![]()
(http://www.microsoft.com/downloads/release.asp?ReleaseID=25444)
119591
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.
(http://support.microsoft.com/kb/119591/EN-US/
)
How to Obtain Microsoft Support Files from Online Services
STATUSMicrosoft 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. PropertiesArticle ID: 260063 - Last Review: October 26, 2006 - Revision: 4.2
|




Back to the top








