As per subject, does any of the GroupDocs.Total components allow loading of MSG file, modification of attachments, and then saving back out as MSG?
Unfortunately, this feature is not currently supported by any GroupDocs products. We will consider adding it.
We will update you after discussing this feature with the team and completing our analysis.
Thanks, meanwhile, I don’t suppose it is possible to call the underlying Aspose.Email APIs directly to achieve this requirement?
Yes, there is no such option unless you have an Aspose.Email license to use the library.
The development team has analyzed this feature and planned to add it to GroupDocs.Conversion for .NET 25.3. It was decided to provide a callback function that you could implement to modify the contents of attachments when converting MSG to MSG.
As soon as the version is available, we’ll let you know.
Would GroupDocs.Conversion be able to also allow email metadata such as recipients, sent timestamp, etc, to be modified during the conversion from MSG to MSG process?
Perhaps GroupDocs.Metadata might be better suited to allow more extensive modification of MSG content, attachments and properties?
Taking into account that you also need to modify MSG content, attachments, and properties, it is reasonable to implement this feature within GroupDocs.Metadata, which already supports updating email fields.
Could you please clarify which set of fields you would like to update so I can pass your request along to the development team?
Besides the standard ones which are already available in GroupDocs.Metadata,
below are the fields of interest which I have yet to test if GroupDocs.Metadata is already able to access and update:
- PR_INTERNET_MESSAGE_ID
- Received Time
- Sent On
- BillingInformation
I believe it should also be possible to access/update custom X-Headers?
Separately, are there any known issues with Rich Text format emails in MSG which contain tables with attachments and images embedded in table cells?
Thanks for the details, we’ll analyze the requirements and update you.
Can you please provide the example MSG file that we could use to check for issues?
The issues you have found earlier (filed as CONVERSIONNET-7500) have been fixed in this update. This message was posted using Bugs notification tool by nikola.yankov
Hello, we have enhanced GroupDocs.Metadata with your requirements.
You can find details in the GroupDocs.Metadata for .NET 25.2 release notes.
Also there is an advanced example that shows how to work with Email fields and attachments.
Currently the enhancements are available in GroupDocs.Metadata for .Net 25.2 (NuGet: .NET Standard 2.1 | .NET Framework ) and will be included in the upcoming release of GroupDocs.Total.
The changes introduced to GroupDocs.Metadata which Igor wrote about in his post are also included into GroupDocs.Total for .NET 25.2.
Please let us know if you have any further questions.
Thanks for the update!
Possible to access Aspose.Email’s MapiMessage “SenderSmtpAddress” property?
Also, possible to access MAPI properties similar to using Aspose.Email’s MapiMessage “GetPropertyString” method?
string creatorSmtpAddress = msg.GetPropertyString(0x5D0A001F); // PR_CREATOR_SMTP_ADDRESS_W
string primarySendAcct = msg.GetPropertyString(KnownPropertyList.PrimarySendAccount.Tag);
Hi @jarrodwee
Currently SenderSmtpAddress is not supported and we are going to add this property along with some other missing properties in context of METADATANET-4124 task. This task will be resolved in the upcoming GroupDocs.Metadata for .NET 25.3 release.
Regarding your second question:
Also, possible to access MAPI properties similar to using Aspose.Email’s MapiMessage “GetPropertyString” method?
We need to perform some more investigations before we plan to implement this feature.
We would like to ask you to confirm that you will still need this approach after trying out our 25.3 release with the missing properties.
Thanks.
Thanks for the update, looking forward to trying out the 25.3 release.