Free Support Forum - groupdocs.com

Image in the email gets cropped


#1

Hi usman, I am using GroupDocs.Viewer(version- 16.11.0.0) and runtime version - v2.0.50727,
while uploading email having large image embedded in it along with text , it is not rendering whole image , it is getting cropped.
tried uploading same email in
https://products.groupdocs.app/viewer
Issue is coming there too.


#2

@ankitaarora,

Please share with us the problematic email file so that we can investigate the issue at our end.


#3

Hi20190826065427092.zip (115.9 KB)

Please find attached zipped problematic email file.


#4

@ankitaarora,

We are able to reproduce your reported issue at our end. For further investigation, we have logged this behavior into our internal Issue Tracking System as VIEWERNET-2022. We shall get back to you as soon as we have any updates for you.

As a workaround, you can set a bigger page size when rendering such documents using EmailOptions.PageSize property as shown in the following code samples:

Using v19.8 or higher

using (Viewer viewer = new Viewer("simple-email.msg"))
{
    PngViewOptions options = new PngViewOptions("page-{0}.png");
    options.EmailOptions.PageSize = PageSize.A2;
    viewer.View(options);
}

Using a version older than v19.8

ViewerImageHandler handler = new ViewerImageHandler();
imageOptions = new ImageOptions(); 
// set output page size
imageOptions.EmailOptions.PageSize = PageSize.A2; 
List<PageImage> pages = handler.GetPages("simple-email.msg", imageOptions);

Note: To use the EmailOptions.PageSize property you will have to upgrade to GroupDocs.Viewer for .NET 18.5 or a higher version.


#5

I have already tried pagesize property, we are using 16.1.1 licensed version for groupdocs viewer.
In this version ,we are not getting pagesize property for email options.
Is there any workaround to do in this version only.


#6

@ankitaarora,

I am afraid that the only possible workaround is to use EmailOptions.PageSize property which is supported by GroupDocs.Viewer for .NET 18.5 and the higher versions. Therefore, we would recommend you to please upgrade the API version.


#7

Ok, thanks for the update.


#8

@ankitaarora,

You’re welcome.