Converting MSG file containing nested MSG attachments showing eval license message

GroupDocs.Conversion Product Family
1

I recall this bug was previously fixed - or perhaps I’m mistaken.
Attached herewith is test.msg which is able to repro the issue.
It is an email which contains an email which contains another email.
The top level email converts fine.
Second level email converts okay too.
The third level email shows “Evaluation Only. Created with Aspose.Email for .NET. Copyright 2002-2025 Aspose Pty Ltd.”

test.zip (40.5 KB)

I’m testing with GroupDocs.Total.NETFramework v25.1.

Code as follows:

            GroupDocs.Conversion.Options.Convert.PdfConvertOptions options = new()
            {
                PdfOptions = new GroupDocs.Conversion.Options.Convert.PdfOptions
                {
                    PdfFormat = GroupDocs.Conversion.Options.Convert.PdfFormats.PdfA_2U
                }
            };

            using GroupDocs.Conversion.Converter converter = new(source);
            converter.Convert(source + ".pdf", options);
2

@jarrodwee

It seems you are encountering an issue with nested MSG attachments during conversion, where the third-level email displays an evaluation license message. This can happen if the licensing is not properly set up or if there are specific limitations with the version you are using.

To address this issue, please ensure that you have applied the license correctly in your application. Here’s a general approach to set the license in GroupDocs.Conversion for .NET:

// Create a License object
var license = new GroupDocs.Conversion.License();

// Apply the license
license.SetLicense("path_to_your_license_file.lic");

Make sure to replace "path_to_your_license_file.lic" with the actual path to your license file. This should be done before any conversion operations are performed.

If you have already set the license and are still facing this issue, it might be worth checking if there are any updates or patches available for the version you are using (GroupDocs.Total.NETFramework v25.1). Sometimes, bugs are fixed in newer releases, so updating to the latest version could resolve the problem.

If the issue persists after these steps, consider reaching out to the GroupDocs support team with the details of your environment and the specific files you are working with, as they can provide more targeted assistance.

For further information, you can refer to the official documentation on licensing and troubleshooting in GroupDocs.Conversion here.

If you have any more questions or need further assistance, feel free to ask!

3

Hello @jarrodwee ,

Thank you for reaching out. Please disregard the previous response, as our bot may occasionally provide incorrect information. We have registered your issue in our system under the ID CONVERSIONNET-7543 and will get back to you with results after further investigation.

4

@jarrodwee ,

Thank you for your patience. We have successfully reproduced this issue and confirmed it as a bug. At the moment, we don’t have an exact timeline for the fix, but rest assured, we will notify you as soon as it is resolved.

5

Thanks, I searched through my paid support tickets and found that this bug which I previously reported was fixed in GroupDocs.Conversion 24.8. Screenshot attached.

image.png (39.8 KB)

It is quite worrisome that old bugs are resurfacing in newer releases.

6

Hello @jarrodwee ,

Did this issue also occur specifically during the conversion of .MSG to .PDF? From the screenshot, it’s not entirely clear. If possible, please provide the Helpdesk ticket number so we can investigate both cases further and work on preventing similar issues in the future.

7

@jarrodwee ,

We have found your ticket on the Helpdesk regarding the licensing message issue. As I mentioned earlier, we will conduct additional research to prevent similar situations in the future. If you have any further questions, please don’t hesitate to reach out to us.