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 the email will receive a notification that the inline image has been stripped.
SD-120284
Fix:
Utilize the provided fix JAR file to address the issue. Now, if the inline image lacks the extension, it then will be appended using the content type.
Note:
Before applying the .fjar file, kindly verify its compatibility in the "Jar Compatibility" section below.
Steps to apply the fix:
1. Download the attached .fjar file.
2. Click here for steps to apply the .fjar file.
3. Restart the application service.
4. 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:
Build | Compatible Jar |
14720 | 9828876_14720_Invalid_Extension.fjar |
14730 | 14730_Invalid_Extension.fjar |
14740 | 14740_Invalid_Extension.fjar |
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 - 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 ...Fix: Mail fetching stops due to invalid characters in the attachment name
Issue: Mail fetching being stopped due to invalid characters "?" , ":" in the filename. In this case, the eml file's subject contains ":" character and so, while uploading the .eml as attachment, error is thrown (Only in windows server) Trace: ...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 - ...