PC Win: Hop Count Setting Is Not Observed by Windows Client

Last reviewed: October 10, 1996
Article ID: Q147368

The information in this article applies to:

- Microsoft Mail for Windows Client 3.2, 3.5

SYMPTOMS

A message sent from the Version 3.5 Microsoft Mail for Windows Client, may result in a non-delivery message similar to the following:

From: POSTMASTER To: < sender of message > Subject: Mail failure Date: Thursday, May 23, 1996 3:22PM

FROM: < sender of message >

TO: < recipient of message >                      DATE: 23-05-96
                                                  TIME: 15:22

SUBJECT: < subject of message >

[003] Message hop count exceeded. Message followed the following route:

  NETCAD/HBPO01
  NETCAD/BUPO01
  NETGRI1/RH02
  NETGRI1/IH01
  NETSIS/WO01
  NETSIS/EUO01
  NETSIS/HUB02
  NETUFE/HUB01
  NETUFE/HUB03
  NETUDI/UDIPO1

while attempting to send to the following addresses:

  <net>/<po>/<mailbox>

CAUSE

The 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 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.

STATUS

Microsoft has confirmed this to be a problem in version 3.05.4102 and prior versions of mssfs.dll. Contact Microsoft Product Support Services for more information on the availability of this fix.

MORE INFORMATION

An alternative to replacing the MSSFS.DLL for each client, would be to reduce the number of mail hops (routings through postoffices) to ensure that mail reaches the destination postoffice prior to 10 hops. This is the preferred solution in cases where it is feasible.

The Microsoft Mail for PC Networks Administrators Guide, Chapter 7, includes a section describing the purpose and method of setting hop count. This setting is designed to affect all client who have mailboxes on the postoffice.

The Microsoft Mail Windows Remote client will set the hopcount to ten on all messages it generates. See companion article Q147471 for more information.

Additional Reference Words: MailPCWin hopcount

KBCategory: kbusage kbbug3.2
KBSubcategory: mssfs.dll
Additional reference words: 4.00

THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: October 10, 1996
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.