Problem while fetching a mail since the mail's boundary value is not enclosed with the double quotes.

Problem while fetching a mail since the mail's boundary value is not enclosed with the double quotes.

Issue:
      The mail will not be fetched/processed since the boundary value of the email is not enclosed within double quotes. javax.mail.internet.ParseException will be thrown. Emails causing this type of error will not be moved to error folder. This issue need to be addressed with the server which sends the mail since the boundary value needs to be enclosed within the double quotes.

Fix for moving mail which causing this type of issue to error folder:
      The parser exception is catched properly in the attached .fjar. Apply the attached .fjar to move these type of mail causing the error to the error folder.

Kindly click here for the steps to apply .fjar.

Note:
 The attached .fjar helps only to move mail to error folder when the mail causing above mentioned issue. Please address this error with the mail sending server to get resolved this issue (The server must send the email where the value of the boundary parameter should be enclosed within double quotes to fetch/process the mail successfully without the above mentioned error).

The attached 14105_9042327_debug.fjar file is compatible only with 14105 build.


                    New to ADSelfService Plus?

                      • Related Articles

                      • List of mail fetching issues and solutions

                        Scenario 1 : Mail fetching issue due to Invalid or No PKIX certificate .   Log traces for Mail Fetching  issues Exception when connecting to store.|javax.mail.MessagingException: sun.security.validator.ValidatorException: PKIX path building failed: ...
                      • Troubleshooting Oauth configuration for mail server settings

                        Oauth in ServiceDesk Plus / AssetExplorer for Mail SDP supports Oauth configuration for Office365 and GSuite mailboxes since 11106 build. Office365 mailboxes can be configured with Oauth authentication using EWS (since 11106) and IMAP / SMTP (since ...
                      • 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 ...
                      • 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: ...