PC Ext: Err Msg: Sending File xxxxxxxx.P1 Failed

 Last reviewed: August 30, 1995
Article ID: Q135902
The information in this article applies to:
  • Microsoft Mail for PC Networks, versions 3.2, 3.2a, and 3.5

SYMPTOMS

When you send a message via the MS-DOS External (MTA) Mail program, it may fail, and you will get the following error message in the SESSION.LOG: 

   Sending File xxxxxxxx.P1 failed
The SYSTEM.LOG will also display: 

   [005] Mail retry count exceeded sending to:
   <network name>      /<postoffice name>

CAUSE

The above error occurs when the MTA is not able to write to either the P1 subdirectory or the INQUEUE3.MBG or INQUEUE3.KEY file at the destination postoffice.

RESOLUTION

Log in as the MTA network user account; make sure the MTA user account can read and write to the MAILDATA \MBG and \KEY subdirectories.

At the destination postoffice MAILDATA subdirectory:

  1. Ensure the P1 subdirectory exists. If it is missing, create the subdirectory. Copy POPULATE.MSM from another postoffice subdirectory, and make this file read only.

  2. Ensure there are no *.OLK files dated earlier than the current date and time. If a file exists, remove the lock, and delete the file.

  3. Ensure the INQUEUE3.MBG and INQUEUE3.KEY files exist and are not corrupted or locked.

Other factors that may contribute to this error are low memory or insufficient disk space at the destination postoffice.

Additional reference words: 3.20 3.20a 3.50
KBCategory: kbenv kberrmsg
KBSubcategory: MailPCExt

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: August 30, 1995
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.