Mail Fetching Failure due to Invalid Inline Image embedded with Invalid MimeContent
Log Trace :
1:36:32:641]|[01-10-2024]|[com.manageengine.servicedesk.mailutils.ModuleHandler]|[INFO]|[277]: module identified : null|
[11:36:32:641]|[01-10-2024]|[com.manageengine.servicedesk.v3api.utils.InlineImageUtil]|[SEVERE]|[277]: text/plain - This file type is not supported|
[11:36:32:641]|[01-10-2024]|[com.manageengine.servicedesk.mail.core.MailScheduleBean]|[INFO]|[277]: __errormail__ : Error Mail is encountered for the first time. Skipping it to process again|
[11:36:32:641]|[01-10-2024]|[com.manageengine.servicedesk.mail.core.fetcher.MailFetcher]|[SEVERE]|[277]: __errormail__ : Error while processing inline image|
Cause :
In some cases, an inline image is received which has content-type apart from the regular Inline image content type. Say for example, some inline images have "text/plain" content-type (which can cause same errors in other email clients too) instead of "image/*" content type. Due to this, our internal validation of Inline Image, will cause failures in fetching that mail.
Fix :
Such problematic Inline images are stripped, and those exceptions are ignored (will print traces in logs) thereby Mails will be fetched successfully.
Steps to apply the fix
Note : Before applying the .fjar file, kindly verify its compatibility in the "Jar Compatibility" section below.
- Download the attached .fjar file.
- Click here for steps to apply the .fjar file.
- Restart the application service.
- Check for the issue.
- 5. If the issue occurs again, enable the email debug in the application, recreate the issue after enabling the email debug then immediately zip the logs (<server_home>\logs folder. For eg: C:\Program Files\ManageEngine\ServiceDesk\logs folder) and share it with us for analysis. If the size of the log file is huge, you can send it to us using our FTP link https://bonitas2.zohocorp.com/. Select the product as "ServiceDesk Plus" and provide the proper ticket number.
Jar Compatibility : 14505
New to ADSelfService Plus?
Related Articles
Mail Fetching Stopped Due to Inline Image Handling
Issue Cause : While fetching a mail, in certain mail servers, cid of inline image is not parsed correctly. Once inline stream is converted to image, cid in src attr will be replaced with image url. cid for uploaded inline image in mail content is not ...Mail Fetching: Inline Images Dropping Due to Invalid Extension
Issue: The inline image's file name from the email doesn't contain the extension. Example: filename = sys_attachment.dosys_id=5bb0751c8303b5dc96a238226daad371 As a result, the inline image gets stripped during the mail fetching process. The sender of ...Mail Fetching - Error while processing attachment and inline image.
Issue During the process of fetching emails, attachments are dropped as a result of the presence of directory traversal characters. Furthermore, an issue arises when processing inline images, this particular error related to inline images results in ...Exception while Processing Inline Image with incorrect file name extension
Reference : #7938623, #8561970 Cause : Inline Images could not be processed with incorrect file name, for example "4d54308871ec465c8233d0f470db0308.do?sys_id=4fdfcb17475c1d50c594c133846d436a" . While constructing the filename in our end, the values ...Inline Images are Not Fetched Properly due to the IsInline Property 'false' assignment
About : For the customers using Microsoft Graph or EWS, Microsoft API returns isInline as "false" for inline images in some environment. There is no known reasons behind this behaviour from their documentation. One such possible reason for this ...