Inbox format

The Inbox file

Below is a Wordpad view of the contents of an inbox file. It contains only three messages. Each message starts with the value "From -" in column one of a new line. There will also be a "From:" in the message, but this is part of the message. The start of a message will be the "From" followed by a space and a dash. The "From" followed by a colon indicates who sent the message. I have colored the starts red to make them stand out. Each message also has an "X-Mozilla-Status" and I have colored them in blue. I have been unable to find a complete list of all the status codes,  but in the samples below, the status codes were "0000" when not yet read, "8001" after reading the message, and "8009" when the message was marked for delete. If this inbox were opened in Messenger, it would indicate "Total messages: 2" and "Unread messages: 1". The first message was read and deleted so it is not reflected in these values. The second message had been read but not deleted, so it shows up in the total. The third message was received but not read. It will be reflected in the 'Total" and "Unread" values.  The first message was deleted, but obviouly, it is still there taking up space, but it is not accessible in Messenger. Little more happened with the delete than for the status code to be changed to "8009", and its status updated in the inbox.snm file. I have also inserted a purple dashed line between messages to separate them. These will not appear in the actual Inbox

The Inbox.snm  file

This Inbox.snm file is a summary/index of the contents of the Inbox file. It is a binary file and cannot be viewed. It is reasonable to assume that this much smaller file is what is displayed in the header section of Messenger. In addition to what is displayed in the header section, it must also have the "X-Mozilla status" code recorded in it . This permits it to display the headers in bold if unread, in normal font if read, and not at all if marked for delete. It must also contain the location of each message within the Inbox. Otherwise, messenger would have to search thru a large file to find the message it is looking for. Since the SNM file is accessed and re-written so often, it is possible for it to be re-written incorrectly resulting in a corrupted file, due to some glitch, or even an error by the RAM. If the SNM file is corrupted, Netscape will likely die when messenger is accessed.  The fix for this problem is to delete the SNM file. When messenger is accessed, it looks for the SNM file and uses it if it exists. If it is bad, then Netscapes could abort. If messenger does not find the SNM file, it will parse the Inbox, and create a new SNM file based on what it finds in the Inbox. Deleting the SNM file when Netscape is not running and letting it create a new one when started will solve the problem if the problem was the SNM file. If the problem is in the Inbox itself, then deleting the SNM file may not fix the problem.
 
 
From - Sun Oct 24 04:32:05 1999 
Return-Path: <cdsops@mindspring.com> 
Received: from smtp10.atl.mindspring.net ([207.69.200.246]) 
 by ngquotad00.atl.mindspring.net (Mindspring Mail Service) with ESMTP id s15hd1.3g4.37kb01n 
 for <cdsops@mindspring.com>; Sun, 24 Oct 1999 04:38:57 -0400 (EDT) 
Received: from mindspring.com (user-37kas3u.dialup.mindspring.com [207.69.112.126]) 
 by smtp10.atl.mindspring.net (8.8.5/8.8.5) with ESMTP id EAA11319 
 for <cdsops@mindspring.com>; Sun, 24 Oct 1999 04:38:56 -0400 (EDT) 
Message-ID: <3812C3BA.72FB0DE8@mindspring.com> 
Date: Sun, 24 Oct 1999 04:30:50 -0400 
From: Joe <cdsops@mindspring.com> 
X-Mailer: Mozilla 4.04 [en] (Win95; I) 
MIME-Version: 1.0 
To: Joe <cdsops@mindspring.com> 
Subject: Message 1 
Content-Type: text/plain; charset=us-ascii 
Content-Transfer-Encoding: 7bit 
X-Mozilla-Status: 8009 

This is the first message. It was read, and then deleted. The X-Mozilla 
Status should read 8009, because it has been read, and then deleted. 
Note that even though deleted, the message remains within the Inbox. 
---------------------------------------------------------------------------------------------- 
From - Sun Oct 24 04:37:24 1999 
Return-Path: <cdsops@mindspring.com> 
Received: from smtp5.mindspring.com ([207.69.200.82]) 
 by mx6.mindspring.com (Mindspring Mail Service) with ESMTP id s15hp2.c5.37kbi14 
 for <cdsops@mindspring.com>; Sun, 24 Oct 1999 04:45:22 -0400 (EDT) 
Received: from mindspring.com (user-37kas3u.dialup.mindspring.com [207.69.112.126]) 
 by smtp5.mindspring.com (8.8.5/8.8.5) with ESMTP id EAA18160 
 for <cdsops@mindspring.com>; Sun, 24 Oct 1999 04:45:21 -0400 (EDT) 
Message-ID: <3812C53A.7C252C10@mindspring.com> 
Date: Sun, 24 Oct 1999 04:37:14 -0400 
From: Joe <cdsops@mindspring.com> 
X-Mailer: Mozilla 4.04 [en] (Win95; I) 
MIME-Version: 1.0 
To: Joe <cdsops@mindspring.com> 
Subject: Message 2 
Content-Type: multipart/mixed; boundary="------------3BAF4463B33D627B123A53EB" 
X-Mozilla-Status: 8001 

This is a multi-part message in MIME format. 
--------------3BAF4463B33D627B123A53EB 
Content-Type: text/plain; charset=us-ascii 
Content-Transfer-Encoding: 7bit 

This message was sent with a 1K JPG attached. The image will be 
displayed in the Inbox with Wordpad as unreadable text. If the attached JPG had been 
more like 1Meg, the unreadable text in the Inbox will go on for page 
after page until the image is complete. This message has been read, but 
not deleted. The X-Mozilla-Status code should be something like 8001. 
--------------3BAF4463B33D627B123A53EB 
Content-Type: image/jpeg; name="joe.jpg" 
Content-Transfer-Encoding: base64 
Content-Disposition: inline; filename="joe.jpg" 

/9j/4AAQSkZJRgABAQEBLAEsAAD/2wBDAAgGBgcGBQgHBwcJCQgKDBQNDAsLDBkSEw8UHRof 
Hh0aHBwgJC4nICIsIxwcKDcpLDAxNDQ0Hyc5PTgyPC4zNDL/2wBDAQkJCQwLDBgNDRgyIRwh 
MjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjIyMjL/wAAR 
CAATADADASIAAhEBAxEB/8QAHwAAAQUBAQEBAQEAAAAAAAAAAAECAwQFBgcICQoL/8QAtRAA          Note - the unreadable text in this area is an attachment.  If the attachment 
was quite large, this unreadable text could be hundreds of pages long. 
AgEDAwIEAwUFBAQAAAF9AQIDAAQRBRIhMUEGE1FhByJxFDKBkaEII0KxwRVS0fAkM2JyggkK 
FhcYGRolJicoKSo0NTY3ODk6Q0RFRkdISUpTVFVWV1hZWmNkZWZnaGlqc3R1dnd4eXqDhIWG 
h4iJipKTlJWWl5iZmqKjpKWmp6ipqrKztLW2t7i5usLDxMXGx8jJytLT1NXW19jZ2uHi4+Tl 
5ufo6erx8vP09fb3+Pn6/8QAHwEAAwEBAQEBAQEBAQAAAAAAAAECAwQFBgcICQoL/8QAtREA 
AgECBAQDBAcFBAQAAQJ3AAECAxEEBSExBhJBUQdhcRMiMoEIFEKRobHBCSMzUvAVYnLRChYk 
NOEl8RcYGRomJygpKjU2Nzg5OkNERUZHSElKU1RVVldYWVpjZGVmZ2hpanN0dXZ3eHl6goOE 
hYaHiImKkpOUlZaXmJmaoqOkpaanqKmqsrO0tba3uLm6wsPExcbHyMnK0tPU1dbX2Nna4uPk 
5ebn6Onq8vP09fb3+Pn6/9oADAMBAAIRAxEAPwD3+iisvVfEOm6HcW6apcx2cE6OVu7h1jgV 
lK/IXYgb2DEqO4Rz2oAuWF9b6np1tf2cnmWt1Ek0L7SNyMAVODyMgjrVivI2ubnS/Ctla3d5 
d6fqFp4Xs20e1Nw9u01+ElDxiMEee4ZbcGNg2NwG35znU1HUNT/4WBPbC9ggmTULVLOOXU5k 
ke1KwmXZZqhSZSTOPNb7p3ElRECAD0iiiigAooooAKKKKACiiigD/9k= 
--------------3BAF4463B33D627B123A53EB-- 
--------------------------------------------------------------------------------------- 
From - Sun Oct 24 04:40:21 1999 
Return-Path: <cdsops@mindspring.com> 
Received: from smtp5.mindspring.com ([207.69.200.82]) 
 by ngquotad00.atl.mindspring.net (Mindspring Mail Service) with ESMTP id s15hug.4oe.37kb01n.1 
 for <cdsops@mindspring.com>; Sun, 24 Oct 1999 04:48:16 -0400 (EDT) 
Received: from mindspring.com (user-37kas3u.dialup.mindspring.com [207.69.112.126]) 
 by smtp5.mindspring.com (8.8.5/8.8.5) with ESMTP id EAA18839 
 for <cdsops@mindspring.com>; Sun, 24 Oct 1999 04:48:15 -0400 (EDT) 
Message-ID: <3812C5E9.AA8B6B76@mindspring.com> 
Date: Sun, 24 Oct 1999 04:40:09 -0400 
From: Joe <cdsops@mindspring.com> 
X-Mailer: Mozilla 4.04 [en] (Win95; I) 
MIME-Version: 1.0 
To: Joe <cdsops@mindspring.com> 
Subject: Message 3 
Content-Type: text/plain; charset=us-ascii 
Content-Transfer-Encoding: 7bit 
X-Mozilla-Status: 0000 

This message has been received, but not read. The X-Mozilla-Status 
should be 0000, indicating not read, and the header would be displayed 
in bold in messenger to indicate 'not read'. 

 
If you attempt to edit the Inbox file, you must do so with Communicator closed. You should also backup the Inbox first in case you really mess things up. Also, you must delete the Inbox.snm file if you change the Inbox. Failure to do so may cause Communicator to abort if it finds differences in the content of the two files.  When Communicator is started, and it finds no SNM file, it will create a new one based on the new contents of the Inbox file.
Possible changes that you might want to make to the Inbox above -
1 - The first message has been marked for 'delete' and you want to make it 'visible' in the the Inbox file. You could change its X-Mozilla-Status from '8009' to '8001' in Wordpad, then resave the Inbox. You would then delete the Inbox.snm file. Starting Communicator and entering Messsenger should then 'display' that message.
2- Whenever you attempt to access message two, Communicator aborts, and you suspect that the attachment is corrupted in some way. You could open the Inbox in Wordpad, and once you locate the message, delete the message.  This would involve a delete starting at the 'From -' line of the message all the way down to the line just in front of the next 'From -' line (the next message).  You would then resave the Inbox, delete the Inbox.snm file, and start Communicator. A new SNM file will be created, and the 'bad' message should no longer be there to cause aborts.
If all this fails to help, you did back up the Inbox right?  With Communicator closed, restore the Inbox file, delete the Inbox.snm file, and restart Communicator. You should be back where you started.
 
 

Back