Converting Msg to Pdf with Pagesize A4 renders a blank page

Converting msg to pdf with defaut PdfConvertOptions settings renders wrong page ratio (very high page), but setting PageSize to A4 renders a blank Pdf page (the file is not empty because the size is not 0ko). We are using dotnet 6 and GroupDocs.Conversion 24.3.0. Here is the code snippet:

ConverterSettings converterSettings = new()
{
    Logger = new GroupDocsLogger(_logger)
};

_formatFichierCible = request.FormatCible;

using Stream sourceStream = new MemoryStream(request.FichierSource.Contenu);

using MemoryStream outputStream = new MemoryStream();

using var converter = new Converter(
    () => sourceStream,
    (sourceType) => new EmailLoadOptions
    {
        ConvertOwner = true,
        ConvertOwned = false,
        Depth = 0
    },
    () => converterSettings);

int index = 0;
converter.Convert(
    () =>
    {
        index++;
        return (index == 1) ? outputStream : new MemoryStream();
    },
    (sourceFileName, targetFileType, convertedFileStream) =>
    {
        _logger.LogDebug($"Le document {sourceFileName} a été converti dans le format {targetFileType}");
    },
    // Provider des options de conversion
    (sourceDocumentName, sourceDocumentType) => new PdfConvertOptions()
    {
        Format = PdfFileType.Pdf,
        PageSize = PageSize.A4
    });

msg.zip (443,1 Ko)

1 Like

@frederic.geslin

Could you please share the problematic MSG and resultant PDF files as well? We’ll then investigate this scenario.

I’ve updated the original post with the problematic MSG and resultant PDF.

1 Like

@frederic.geslin
This issue is reproduced at our end. It’s been observed that this issue appears when we set PdfConvertOptions e.g. Format and PageSize. 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): CONVERSIONNET-6820

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.

The issues you have found earlier (filed as CONVERSIONNET-6820) have been fixed in this update. This message was posted using Bugs notification tool by nikola.yankov