Mail fetching failure when incoming mail contains delimiter of module other than Request & change and Unsupported Release module

Mail fetching failure when incoming mail contains delimiter of module other than Request & change and Unsupported Release module

When processing a incoming mail that contains a delimiter of module other than Request & change and the License applied in the environment that doesn't have access to Release module, then the following mail fetching failure issue will occur.

Reference Traces :
  1. [14:23:32:678]|[12-28-2023]|[com.manageengine.servicedesk.v3api.utils.AttachmentAPIUtil]|[SEVERE]|[532]: Unexpected error occurred in attachment handling| 
  2. com.manageengine.sdpod.v3api.SDPAPIException
  3. at com.manageengine.sdpod.v3api.handler.AbstractEntityHandler.checkLicenseRestrictions(AbstractEntityHandler.java:355)
  4. at com.manageengine.sdpod.v3api.handler.AbstractEntityHandler.handleAPICall(AbstractEntityHandler.java:97)

Cause of this Issue : 
      During mail fetching, if the incoming mail has attachments, module for the APIRequest is identified. In that process, If the incoming mail has no delimiter or Request delimiter or Change delimiter, APIRequest module is considered as Release. This is what the root cause for this issue. 
      Since the customer environment do not have license to Release module, the above exception will be thrown, which inturn result in mail fetching failure.

Resolution :
  1. We can resolve this issue by considering Request as the default APIRequest module, which can be achieved with the attached fjar. Refer here to know how to apply fjar.
  2. We have considered this as an issue and it will be fixed in our upcoming releases. (Refer Notes section for Issue id)
Notes: 
  1. Issue Id to be released in 14730 : SD-117884
  2. Fjar compatible versions
    1. Build Version
      Compatible fjar name
      14505-14600
      14506_delimiter_module.fjar
      14720
      14720_delimiter_module.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 ...
                      • 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 ...
                      • 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: ...