PC Rmt: Err Msg: ProcessRecvMail, fp_read Fails. Out of Memory

Last reviewed: April 19, 1996
Article ID: Q149368
The information in this article applies to:
  • Microsoft Mail Remote for MS-DOS, version 3.0

SYMPTOMS

When you try to retrieve a message addressed to 300 or more total individual recipients, during the retrieval of the message, you may get the following error message:

   ProcessRecvMail, fp_read fails.
   Out of memory.

CAUSE

When you retrieve a message addressed to 300 or more individually addressed recipients, the MS-DOS Mail Remote client may encounter a memory limitation that results in the above error message.

NOTE: Other mail messages pending in the your mailbag will be retrieved successfully during the session. However, the client will have to exhaust the number of required retry attempts on the failing message to eliminate the error condition and have the message returned to the originator with a non-delivery report.

RESOLUTION

This problem can be corrected by creating a group definition on the postoffice that contains the desired recipient list. Therefore, the retrieval of the message by the MS-DOS Mail Remote client will not fail if the same number of recipients are delivered via a group alias.


Additional reference words: 3.00 DOS remote
KBCategory: kbenv kberrmsg
KBSubcategory: MailPCRmt


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: April 19, 1996
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.