The information in this article applies to:
SYMPTOMSA mail message sent from the Version 3.2 of Microsoft Mail Remote for Windows version 3.2 or 3.5 client, may result in a non-delivery message similar to the following:
CAUSEThe non-delivery report is generated when the number of hops reaches ten, regardless of the hop count setting as configured in the Admin program. The Remote Windows client does not pick up the administrator set hop count from the postoffice. The client inserts a hop count of ten in all messages. RESOLUTION
A supported fix that corrects this problem is now available from Microsoft,
but has not been fully regression tested and should be applied only to
systems experiencing this specific problem.
http://support.microsoft.com/support/supportnet/default.aspThe English version of this fix should have the following file attributes or later:
This hotfix has been posted to the following Internet location as
Remcy2k.exe:
ftp://ftp.microsoft.com/bussys/mail/pcmail-public/All-Y2K/ STATUSMicrosoft has confirmed this to be a problem in Microsoft Mail Remote for Windows version 3.2. MORE INFORMATION
The Windows Remote Client has no access to the hop count as set by the
administrator on the home postoffice. The 3.05.0030 version of external
implements code to insert the postoffice value of hop count into remote
client messages. Prior versions of external did not change the value of
hop count when handling remote client messages.
Additional query words: MailPCWRmt hopcount MailPCWin MailPCMMTA
Keywords : MailPCExt external.exe |
Last Reviewed: January 21, 2000 © 2000 Microsoft Corporation. All rights reserved. Terms of Use. |