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:
[12:01:48:189]|[06-10-2024]|[com.manageengine.servicedesk.mail.core.fetcher.EwsMailFetcher]|[INFO]|[342]: Going to process using MIME ?::true|
[12:01:48:189]|[06-10-2024]|[com.manageengine.servicedesk.mailutils.MailAPI]|[INFO]|[342]: Failed to decode. So returning {1}|
[12:01:48:189]|[06-10-2024]|[com.manageengine.servicedesk.mail.core.fetcher.EwsMailFetcher]|[SEVERE]|[342]: Error in accessing : message[12]|
[12:01:48:189]|[06-10-2024]|[SYSERR]|[INFO]|[342]: java.io.UnsupportedEncodingException: iso-8859-8-i|
[12:01:48:189]|[06-10-2024]|[SYSERR]|[INFO]|[342]: at java.lang.StringCoding.decode(StringCoding.java:190)|
[12:01:48:189]|[06-10-2024]|[SYSERR]|[INFO]|[342]: at java.lang.String.<init>(String.java:426)|
[12:01:48:189]|[06-10-2024]|[SYSERR]|[INFO]|[342]: at javax.mail.internet.MimeUtility.decodeWord(MimeUtility.java:924)|
[12:01:48:189]|[06-10-2024]|[SYSERR]|[INFO]|[342]: at javax.mail.internet.MimeUtility.decodeText(MimeUtility.java:627)|
[12:01:48:189]|[06-10-2024]|[SYSERR]|[INFO]|[342]: at com.manageengine.servicedesk.mailutils.MailAPI.decodeMime(MailAPI.java:2722)|
[12:01:48:189]|[06-10-2024]|[SYSERR]|[INFO]|[342]: at com.manageengine.servicedesk.mail.core.fetcher.EwsMailFetcher.fetchAndProcessMails(EwsMailFetcher.java:117)|
[12:01:48:189]|[06-10-2024]|[SYSERR]|[INFO]|[342]: at com.manageengine.servicedesk.mail.core.fetcher.MailFetcher.startFetching(MailFetcher.java:306)|
[12:01:48:189]|[06-10-2024]|[SYSERR]|[INFO]|[342]: at com.adventnet.servicedesk.helpdesk.mail.task.MailFetchingTask.executeTask(MailFetchingTask.java:39)|
[12:01:48:189]|[06-10-2024]|[SYSERR]|[INFO]|[342]: at com.adventnet.taskengine.internal.SchedulerBean.executeTask(SchedulerBean.java:698)|
Error trace for POP or IMAP:
[11:13:12:885]|[06-06-2024]|[com.manageengine.servicedesk.mailutils.MailAPI]|[INFO]|[303]: Failed to decode. So returning {1}|
[11:13:12:885]|[06-06-2024]|[com.manageengine.servicedesk.mail.core.fetcher.JavaMailFetcher]|[SEVERE]|[303]: Error in accessing : message[0]|
Fix:
Use the provided fix JAR file to resolve the issue. This solution ensures proper decoding of the subject.
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 | 14720_10053503_subject_decode_java_ews.fjar |
14740 & 14750 | 14750_subject_decode_ews_java.fjar |
New to ADSelfService Plus?
Related Articles
Mail fetching issue_Remote host closed connection during handshake
GUI Error Trace: FAILURE :E-mail settings saved successfully. But error occurred while trying to check connection with mail server - Problem connecting to mailbox. LOG TRACE: [16:33:06:197]|[11-09-2018]|[SYSERR]|[INFO]|[120]: ...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 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 ...Failure during Zia Reopen prediction process stops the mail fetching schedule
When the requester replies to closed/resolved requests with empty content or if there is no proper content except the content of the parent mail, then no content will be available for zia reopen prediction process and an exception will be ...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 ...