I am finding that multiple e-mails in my environment that I am using for testing (some of which contain an extreme amount of inline and regular attachments) only report 3 attachments once I place the item into a PST.
For example, from some of my application output:
Reading msg: C:\temp\aspose\msg\402ec7d9-9ace-4530-b313-9c5b1e5549ab.msg
Adding to PST… success!
Attachment failure - number of attachments incorrect within PST! (37 / 3)
In this case, 37 is the number of attachments in the source, and 3 is the number of attachments after verifying the item in the PST. All items that fail in this manner report the same number of attachments in the new item in the PST. Out of 4792 items, I have the following error log:
Attachment failure - number of attachments incorrect within PST! (37 / 3)
Attachment failure - number of attachments incorrect within PST! (8 / 3)
Attachment failure - number of attachments incorrect within PST! (4 / 3)
Attachment failure - number of attachments incorrect within PST! (4 / 3)
Attachment failure - number of attachments incorrect within PST! (37 / 3)
Attachment failure - number of attachments incorrect within PST! (5 / 3)
Attachment failure - number of attachments incorrect within PST! (4 / 3)
Attachment failure - number of attachments incorrect within PST! (4 / 3)
Attachment failure - number of attachments incorrect within PST! (4 / 3)
Attachment failure - number of attachments incorrect within PST! (5 / 3)
Attachment failure - number of attachments incorrect within PST! (4 / 3)
Attachment failure - number of attachments incorrect within PST! (4 / 3)
Attachment failure - number of attachments incorrect within PST! (5 / 3)
Attachment failure - number of attachments incorrect within PST! (4 / 3)
Attachment failure - number of attachments incorrect within PST! (4 / 3)
Attachment failure - number of attachments incorrect within PST! (4 / 3)
Verify failures: 16
Is this some kind of limitation in the “demo”?
Thank you for your time.
Hi Massimo,
Thank you for using Aspose.Email.
You are right in that these are evaluation limitations imposed by the API as mentioned in our online documentation section Evaluate Aspose.Email. However, I would like to share that we facilitate our users to try the API without any evaluation limitations by requesting a 30-day free temporary license. Please let us know if we can be of any additional help to you in this regard.
I apologize greatly for wasting your time. I did not see the evaluation restrictions page containing all of that information previously when I was using this library for evaluation and originally downloaded the software.
This also explains a GREAT many things that I have seen in the product itself that I thought were simply “quirks”. Hah! I have requested a 30 day temp license to perform actual tests now for some of this data.
Thank you again.
Hi Massimo,
Thank you for the feedback and please feel free to write to us in case you have any other query/inquiry in this regard.