DOCUMENT:Q87417 05-NOV-1999 [pcmail] TITLE :PC DB: Rebuilding an MBG File PRODUCT :Microsoft Mail For PC Networks PROD/VER:WINDOWS:2.1e,3.0,3.2 OPER/SYS: KEYWORDS: ====================================================================== ------------------------------------------------------------------------------- The information in this article applies to: - Microsoft Mail for PC Networks, versions 2.1e, 3.0, 3.2 ------------------------------------------------------------------------------- SUMMARY ======= It is very difficult to rebuild an MBG file. The file is not encrypted and the contents of the mail headers can be read. To rebuild an MBG file, it would be necessary for the recovered headers to align on 116-byte boundaries and the proper MAI filename to be in the correct location. The matching KEY file would have to be synchronized to the rebuilt MBG file. This process would be completely manual, because there is no utility to help recover the header information. In most cases, the only solution is to restore from a backup file. Microsoft does not recommend rebuilding an MBG file unless no backups are available, and the mail is too important to lose. Additional query words: 2.10e 3.00 3.20 ====================================================================== Keywords : Technology : kbMailSearch kbZNotKeyword3 kbMailPCN320 kbMailPCN300 kbMailPCN210e Version : WINDOWS:2.1e,3.0,3.2 ============================================================================= 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. Copyright Microsoft Corporation 1999.