Issue Summary

Jira incoming mail processing creates duplicate tickets from SharePoint emails because the source email is not being marked as read after the initial issue creation. This occurs because the SharePoint email's message-ID exceeds 255 characters, causing the database "store" operation to fail, which in turn prevents the "mark as read" action from executing.

This will affect any email whose message-ID is greater than 255 characters. It's not limited to SharePoint emails. 

Steps to Reproduce

• Configure a Jira incoming mail handler to create work items from an incoming mailbox.
• Send an automated SharePoint notification email (which typically has a very long message-ID) to that mailbox.
• Observe that Jira creates the initial issue successfully.
• But leaves the original email unread in the mailbox.
• Wait for the mail handler's next polling cycles (typically every hour).

Expected Results

Jira should mark the email as read after the first successful issue creation, preventing it from being reprocessed.

Actual Results

The email remains unread in the mailbox. Jira's duplicate detection suppresses it for approximately one hour, but eventually fails to match the existing issue and creates a new duplicate ticket were created from the same email.

Workaround

Manually mark the SharePoint emails as Read in the source mailbox to stop the mail handler from picking them up again. Currently, there is NO automated workaround within Jira settings