Atlassian uses cookies to improve your browsing experience, perform analytics and research, and conduct advertising. Accept all cookies to indicate that you agree to our use of cookies on your device. Atlassian cookies and tracking notice, (opens new window)
The Plugin People
Teams
, (opens new window)

Knowledge Base
  • How-to articles
    How-to articles
     This trigger is hidden
Results will update as you type.
  • Enterprise Mail Handler - JEMH - (Server/DataCenter)
    • Auditing History purge does not work with "Retain Failures" enabled (JIRA 7.x)
    • Concurrent mail retrieval resulting in duplicate issue creation
    • Configuration screen won't save updates
    • Creating duplicate issues to multiple projects fails
    • Diagnosing Slow or Stopped Incoming Mail
    • Duplicate issues are created when using JEMH and JIRA Data Center
    • Email client shows encoded attachment name instead of decoded file name
    • Enable Auto Labelling
    • Event Listener JSD issue transition notifications do not send if a comment is present in the transition
    • Exception during issue update validation for non-Service Desk issue
    • File Attachments cause Out Of Memory problems
    • Gmail confidential mode
    • How to supply a default value for the Tempo Account custom field
    • How to support email addresses with international characters
    • Issue fails to create with indexing errors
    • JEMH Is not yet licensed through Atlassian Marketplace
    • JIRA fires Issue Assigned event for newly created Issues
    • Jira Service Desk problems
    • Jira 7 *Wrong JVM Version!* Error
    • JSD Organization field
    • Mail fails to be retrieved from mail server
    • MYSQL exception - Caused by: java.sql.SQLException: Incorrect string value
    • MYSQL Duplicate entry '0'. No Valid License
    • Non-JIRA recipient custom field values have been updated but JEMH is notifying the old values
    • Notification History tab does not show on issues
    • Problems with IMAP
    • Problems with POP
    • Slow Jira startup with PostgreSQL
    • Sorry, you can't create any issues right now, as you need to have access to a JIRA application to be able to create issues
    • You do not have permission to assign issues
    • How to change the event type of a notified event
    • Diagnose no inbound mail handled
    • JSD (Jira Service Desk) - Who is notified when?
    • HTML extraction method to Wiki mark up
    • Setting System Fields using Script Field Processor
    • Test case editor fails to load
    • MessageRemovedException in log files during email processing
    • Characters appearing as question marks
    • UI not visible after upgrading to version 3+
    • Default Project Mapping and unwanted inheritance causing inbound mail to be forwarded
    • JEMH is disabled on startup in Manage Apps
    • Configure JSD Customers for use with JEMH
    • Custom Field values are cached causing recipients to not receive notifications (JIRA 7.3.0 - 7.3.4 , JEMH 2.1.0 - 2.1.11)
    • Restrict commenting to one project
    • Foreign key constraint violation during Audit Event history purge
    • Request participants not sent JEMH notification
    • Handling out of disk space
    • Profile import timeout error
    • Zendesk integration
    • Outlook sending formatting
    • Attachment links added as comments, Jira Service Management/Desk
    • Incoming Auditing Actions Error Popup
    • Updating JEMH's issue event listener to listen for IssueEventBundle's (JEMH-6994)
    • Template Set Responsibility Devolution (JEMH-5403)
    • Support non-ascii characters in email addresses (JEMH-6431)
    • Custom Fields don't get added during creation phase causing creation notifications to not fire for User/Group field types. (JEMH-306)
    • Cant stop reporter being added as a watcher (JEMH-790)
    • Handle re-index failure during watcher setup (JEMH-7180)
    • Inline User Macros sometimes don't render (velocity 2.0 needed) (JEMH-5536)
    • "Stuck" emails in queues after post condition test (JEMH-5366)
    • Dealing with 'Undisclosed Recipients' (JEMH Server/DC)
    • Missing Methods in TemplateIssue Class since Jira 8.19.0
    • Why do FolderClosedException occur
    • Customer Permissions for Request Participants
    • User Anonymization Fails - SQL Server 2019
    • Maintaining JEMH Attachment Property Set values
    Calendars
You‘re viewing this with anonymous access, so some content might be blocked.
/
Problems with IMAP
Updated Nov 05, 2020

    Problems with IMAP

    Problem

    You occasionally have messages that won't process, and are using an IMAP mail server.

    Folder Closed / Repeat Processing

    IMAP is touted as a more advanced protocol than POP, which is true in some regards, but in some scenarios it can be problematic (see link below).  If you experience FolderClosedException, which are due to your mailserver closing the connection on the mail being retrieved. Causes of FolderClosed include too many concurrent logins via multiple inbound mail server configurations for the same mailbox and mail that is too large for the default IMAP data batching data sizes used for retrieval. See the link below for some anecdotal performance results, and further details of what you can do to change your environment to work better with large mails over IMAP.

    • https://thepluginpeople.atlassian.net/wiki/spaces/JEMH/pages/57606174

    JEMH operates with a limited interface to Jira, we have raised this with Atlassian to improve their API, please watch/vote:

    • https://jira.atlassian.com/browse/JRA-60200

    Message Removed

    If you have concurrent access to a common mailbox its possible that a message may be 'removed' by another handler process, the error is likely to be harmless, unless the configuration caused the message to be dropped.

    Performance Issues

    We have found that there can be significant performance problems with IMAP when it is dealing with large messages. Take a look at our POP vs IMAP performance page, where we also give advice on what you can do to resolve the problem:

    • https://thepluginpeople.atlassian.net/wiki/spaces/JEMH/pages/57606174

    Solution

    • Check your mailbox for large messages. It is possible they are not able to be downloaded in time, possibly being timed-out by a mail server or JIRA.

    • Consider trying POP. It is better suited for JIRA usage as mail handlers require reliable transmission of the entire email, rather than partial transmission which is what IMAP is useful for.

    Related articles

    • Page:
      Diagnose no inbound mail handled
    • Page:
      JSD Organization field
    • Page:
      How to supply a default value for the Tempo Account custom field
    • Page:
      Enable Auto Labelling
    • Page:
      Jira's Inbound Mail Processing fails due to Basic Authentication Deprecation







    {"serverDuration": 14, "requestCorrelationId": "7fa62b1e42d64f7e930f8638dfc5ff71"}