EML Export from Storage Location in MailStore <11

2024-08-02T00:00:00+00:00

Storage Locations created in MailStore 10 or earlier can be exported to EML files using the internal metadata. This is useful if the database is corrupt and cannot be repaired, as the EML files can be used to re-archive the messages into a new storage location.

This article applies to MailStore 10 and earlier only, as of MailStore 11 an entirely different process is used for recovering from a damaged FDB database.

MailStore 11</a> introduced new recovery records, this article only applies to Storage Locations created with MailStore 10 or earlier, that have not been upgraded to MailStore 11 or later.

If you have a damaged MailStore Storage Location's FDB file (prior to MailStore 11), it is often possible to recover and export the messages from the database using the internal recovery records.

For the purposes of this article, we will assume the following paths:

description</th> example path</th></tr></thead>

Damaged Storage Location</td> C:\MailArchive\2018-03</code></td></tr>

EML export destination</td>

description</th>	example path</th></tr></thead>
Damaged Storage Location</td>	`C:\MailArchive\2018-03</code></td></tr>`
EML export destination</td>	D:\EML</code></td></tr> </tbody></table> Prepare the environment:</p> Avoid using network drives for storing files.</li> Use locally mounted drives (ideally SAS, NVMe, SATA, or iSCSI). Avoid external storage such as USB drives and network paths.</li> For performance reasons, consider placing the Storage Location and EML export destination on separate physical drives.</li> Ensure you have ample free space. It's recommended to have at least double the size of the corrupted storage location available, but more may be needed in certain cases.</li> </ol> </li> Prepare MailStore Server:</p> If you have any Archive E-mail</em> profiles configured to run automatically they may re-archive messages from the original source, so it is recommended to disable all archiving profiles during this process.</li> Shut down MailStore Server completely or detach the problematic storage location to ensure it's not in a failed state.</li> </ol> </li> Run the Recovery Command:</p> Launch a Windows command prompt, enter the following command, substituting paths as necessary:</p> "C:\Program Files (x86)\deepinvent\MailStore Server\MailStoreServer_x64.exe" --recover --inputDir="C:\MailArchive\2018-03" --outputDir="D:\EML" </code></pre> </li> Wait for MailStore to process all DAT</em> files, extracting each to EML</em> files.</p> </li> </ol> </li> Re-Archiving Process:</p> (Optional)</em> Create a new Storage Location (MailStore Client</em> > Administrative Tools</em> > Storage</em> > Storage Locations</em> > Create Storage Location</em>).</li> Go to Archive E-mail</em> > Create a new profile, select EML and MSG Files</em> (or Directory (File System)</em>) files as the source.</li> Choose the MailStore Export</em> option to re-archive the messages back to their correct location.</li> Ensure the corrupted storage location is not attached during this process otherwise messages may be skipped.</li> </ol> </li> Post-Recovery Cleanup:</p> Once you verify the results, delete the corrupt storage location and the EML export destination. directory.</li> </ol> </li> </ol> The extracted EML</em> files can be used with email software that supports EML format, or MailStore itself.</p> 🔗</a>Encryption Keys</h2> MailStore will attempt to read the keys from the FDB</em> database files on disk if not specified, but if the database is corrupt it may not be possible to retrieve the keys automatically.</p> You can add the --securityKey</code> and/or --masterKey</code> parameters to the command line to specify the security and master keys as needed. Please contact support if you need assistance retrieving the keys as this process varies depending on the version of MailStore (and may not be possible in all cases).</p> MailStoreServer.exe --recover --inputDir="C:\FileGroup1" --outputDir="D:\EML" [--securityKey="..."] [--masterKey="..."] </code></pre> 🔗</a>Notes</h2> EML</em> files are created with X-MailStore-*</code> headers that contain metadata to allow for re-archiving or other analysis.</li> EML</em> files can be: Re-archived into the correct location in MailStore.</li> Opened and accessed by any email software that supports EML</em> files, like Thunderbird.</li> </ul> </li> DAT</em> files contain fragments from various messages.</li> Messages in DAT</em> files are not always in sequential order.</li> You may attempt to perform an export on an incomplete set of DAT</em> files, only valid messages will be exported.</li> You may restore or replace DAT</em> files and then export again to fill in missing messages if further DAT</em> files are available.</li> Exporting again will create duplicate EML</em> files, but these will be skipped by MailStore when re-archiving.</li> Special Case: Storage Locations created in MailStore 10 or earlier, but with messages added by MailStore 11, may not export completely with this process.</li> In such cases, contact MailStore support for assistance.</li> </ul> </li> </ul>

D:\EML</code></td></tr>
</tbody></table>


Prepare the environment:</p>

Avoid using network drives for storing files.</li>
Use locally mounted drives (ideally SAS, NVMe, SATA, or iSCSI). Avoid external storage such as USB drives and network paths.</li>
For performance reasons, consider placing the Storage Location and EML export destination on separate physical drives.</li>
Ensure you have ample free space. It's recommended to have at least double the size of the corrupted storage location available, but more may be needed in certain cases.</li>
</ol>
</li>

Prepare MailStore Server:</p>

If you have any Archive E-mail</em> profiles configured to run automatically they may re-archive messages from the original source, so it is recommended to disable all archiving profiles during this process.</li>
Shut down MailStore Server completely or detach the problematic storage location to ensure it's not in a failed state.</li>
</ol>
</li>

Run the Recovery Command:</p>


Launch a Windows command prompt, enter the following command, substituting paths as necessary:</p>
"C:\Program Files (x86)\deepinvent\MailStore Server\MailStoreServer_x64.exe" --recover --inputDir="C:\MailArchive\2018-03" --outputDir="D:\EML"
</code></pre>
</li>

Wait for MailStore to process all DAT</em> files, extracting each to EML</em> files.</p>
</li>
</ol>
</li>

Re-Archiving Process:</p>

(Optional)</em> Create a new Storage Location (MailStore Client</em> > Administrative Tools</em> > Storage</em> > Storage Locations</em> > Create Storage Location</em>).</li>
Go to Archive E-mail</em> > Create a new profile, select EML and MSG Files</em> (or Directory (File System)</em>) files as the source.</li>
Choose the MailStore Export</em> option to re-archive the messages back to their correct location.</li>
Ensure the corrupted storage location is not attached during this process otherwise messages may be skipped.</li>
</ol>
</li>

Post-Recovery Cleanup:</p>

Once you verify the results, delete the corrupt storage location and the EML export destination. directory.</li>
</ol>
</li>
</ol>
The extracted EML</em> files can be used with email software that supports EML format, or MailStore itself.</p>
🔗</a>Encryption Keys</h2>
MailStore will attempt to read the keys from the FDB</em> database files on disk if not specified, but if the database is corrupt it may not be possible to retrieve the keys automatically.</p>
You can add the --securityKey</code> and/or  --masterKey</code> parameters to the command line to specify the security and master keys as needed. Please contact support if you need assistance retrieving the keys as this process varies depending on the version of MailStore (and may not be possible in all cases).</p>
MailStoreServer.exe --recover
     --inputDir="C:\FileGroup1"
     --outputDir="D:\EML"
    [--securityKey="..."]
    [--masterKey="..."]
</code></pre>
🔗</a>Notes</h2>

EML</em> files are created with X-MailStore-*</code> headers that contain metadata to allow for re-archiving or other analysis.</li>
EML</em> files can be:

Re-archived into the correct location in MailStore.</li>
Opened and accessed by any email software that supports EML</em> files, like Thunderbird.</li>
</ul>
</li>
DAT</em> files contain fragments from various messages.</li>
Messages in DAT</em> files are not always in sequential order.</li>
You may attempt to perform an export on an incomplete set of DAT</em> files, only valid messages will be exported.</li>
You may restore or replace DAT</em> files and then export again to fill in missing messages if further DAT</em> files are available.</li>
Exporting again will create duplicate EML</em> files, but these will be skipped by MailStore when re-archiving.</li>
Special Case:

Storage Locations created in MailStore 10 or earlier, but with messages added by MailStore 11, may not export completely with this process.</li>
In such cases, contact MailStore support for assistance.</li>
</ul>
</li>
</ul>

mailstore-notes.dwlab.me - outdated version

EML Export from Storage Location in MailStore <11