Free Support Forum - aspose.com

Licensing question for MSG conversion

Hi,

We are in the process of evaluating Apose for MIME to MSG content conversion. We have the following questions:

- Are there any performance/scalability numbers that you can share with us for this library

- MSG is a MS proprietary format. Are there any licensing liabilities on us as a consumer. How has Aspose taken care of this.

Thanks

Preeti


This message was posted using Page2Forum from Aspose.Network for .NET - Documentation

Hi Preeti,

Thank you for inquiry.

Regarding performance, we tested with some large files and below were the results:

File Size Class/Method Name Scenario Description Time Consumed Comments
PST - 5 MB PersonalStorage Load PST file, read all the folders/sub-folders and extract/save all the messages. 3.5 sec PST contains Inbox folder and some messages
PST – 450 MB PersonalStorage 13 min 21 sec Large PST file with 1000+ messages, notes and address book entries. Contains some complex messages with embedded MSG attachments, images and other type of documents
MSG – 30 MB MailMessage.Load()
Attachment.Save()
Load MSG file and extract/save all attachments 24.6 sec Very complex MSG file with 50+ embedded messages, word, pdf, images and other documents
MSG – 50 MB MailMessage.Load()
Attachment.Save()
Load MSG file and extract/save all attachments 6.5 sec Contains 2 large attachments, no embedded messages
MSG -30 MB MapiMessage.FromFile()
MapiAttachment.Save()
Load MSG file and extract/save all attachments 8.6 sec Very complex MSG file with 50+ embedded messages, word, pdf, images and other documents
MSG -50 MB MapiMessage.FromFile()
MapiAttachment.Save()
Load MSG file and extract/save all attachments 0.7 sec Contains 2 large attachments, no embedded messages


It depends on the nature of the file, as you can see that complex messages take longer to load/convert. Please also note that the above tests were executed on a low end system (Core i3 2.13 GHz CPU). The performance will be good for better CPU.

Microsoft has opened and published the specifications of files like doc, xlx, msg, pst etc, so that anyone including vendors like us (Aspose) could manipulate these files. There is no licensing liability for you.