"From" MSG to MIME conversion issue

Aspose.Email Product Family
1

Hello,

There is an issue when converting some specific MSG into MIME messages, using the Apose.Email for C# API.

The PST you will find as an attachment only contains one MSG. When trying to convert the latter into a MBOX file, this single MSG will be displayed as two distinct MIME messages in Thunderbird.

The reason why is the presence of the “From” word in the body of the message, which is detected as a header, and therefore as a new message by Thunderbird.

In order to avoid this issue, the “From” word in the body should be changed into “>From” when proceeding to the conversion. This is called “From-mumge” as you can read in the MBOX wikipedia article : Mbox - Wikipedia

When adding the “>” before the “From”, Thunderbird displays the MIME message correctly as one single message.

The code to convert the PST into a MBOX is:

using (var pst = PersonalStorage.FromFile(currentPstPath))
{
    var folderInfo = pst.RootFolder;
    MboxrdStorageWriter writer =  new MboxrdStorageWriter(mboxPath, false);
    var options = new MailConversionOptions();
    foreach (var msg in folderInfo.EnumerateMapiMessages())
    {
        writer.WriteMessage(msg.ToMailMessage(options))
    }
    writer.Dispose();
}

Best regards.
Some2Buy.zip (16,3 Ko)

2

@anthonypr
We have opened the following new ticket(s) in our internal issue tracking system and will deliver their fixes according to the terms mentioned in Free Support Policies.

Issue ID(s): EMAILNET-41358

You can obtain Paid Support Services if you need support on a priority basis, along with the direct access to our Paid Support management team.

3

Thank you for your answer.

Please note this problem only appears when "From " (with a space at the end) is the first word of a new line. Otherwise, "From " can be any part of the body text without raising an issue.

Other remark, after tests Thunderbird will not split the message in the presence of "from " (f lower case) or "FROM " (whole upper case), only "From ".

Regards.

4

Thank you for the additional info. I have added it to the ticket.

5

Hello, is this issue fixed yet?

6

@ariamehr ,

Yes, the issue has been fixed.