Fix JAR for Parse Error Exception Raised during Mail Fetching
Issue :
Some mail are fetched and created as ticket without description due to message corruption temporarily. The issue is can be identified with the below trace.
Fix :
The issue is not recreated when the mail is skipped to next schedule and fetched again.
Error Trace :
- [10:02:11:958]|[09-01-2022]|[SYSOUT]|[INFO]|[1378]: -ERR Message corrupted|
- [10:02:11:958]|[09-01-2022]|[com.manageengine.servicedesk.mail.core.ProcessMailMessage]|[INFO]|[1378]: com.adventnet.servicedesk.mailutils : processMailContent()|
- [10:02:11:958]|[09-01-2022]|[com.manageengine.servicedesk.mail.core.ProcessMailMessage]|[SEVERE]|[1378]: javax.mail.MessagingException|
- [10:02:11:958]|[09-01-2022]|[com.manageengine.servicedesk.mail.core.ProcessMailMessage]|[SEVERE]|[1378]: Exception in multipart/* - mp.getCount()......|
- [10:02:11:958]|[09-01-2022]|[SYSERR]|[INFO]|[1378]: javax.mail.MessagingException: No inputstream from datasource;
- nested exception is:
- java.io.IOException: can't retrieve message #1 in POP3Message.getContentStream|
- [10:02:11:958]|[09-01-2022]|[SYSERR]|[INFO]|[1378]: at javax.mail.internet.MimeMultipart.parse(MimeMultipart.java:600)|
FJAR Description :
- FJAR Handles the parse error mentioned above while fetching mails by catching the messaging exception, The same mail will be fetched in the next schedule without any error.
![](https://img.zohostatic.com/zde/static/images/exclamation.png)
Jar Compatibility
Build No | File Name |
12007 | 1_Empty_Description.fjar |
14006 | 14006_8499371.fjar |
New to ADSelfService Plus?
Related Articles
Debug JAR for Exception Trace While Parse Error Exception Raised during Mail Fetching
Build Compatibility : 12007 FJAR Description : FJAR Handles the parse error while fetching mails by catching the messaging exception, notifying the administrator & technicians (Configured in Notification Rules - Send when Application Error Occurs). ...
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 ...
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: 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: Inability in Decoding 'iso-8859-8-i' Encoded Subjects Results In Mail Fetching failure
Issue: Mail fetching fails when the subject is encoded with 'iso-8859-8-i' due to the inability to decode the subject. This issue occurs across IMAP, POP, and EWS configurations. Issue ID: SD-120959 Error Trace for EWS: ...