Platform notice: Server and Data Center only. This article only applies to Atlassian products on the Server and Data Center platforms.

Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.

*Except Fisheye and Crucible

Symptoms

Symptoms include:

1. Jira users are receiving notifications from Jira issue ABC-5, while this issue does not actually exist in the Jira application
2. Users receive an email that seems to be coming from an automation rule even though that rule was disabled in the Jira application
3. Users sends an email to the Jira application to create a new Jira issue via email but the new issue does not get created in Jira
4. Users create a Jira issue via email but the issue created in Jira has an unexpected issue key

Cause

More than one Jira instance is running, with the same set of projects, same base URL, and with the same email services listening to the same POP3 accounts. One of the instances is actually running at the base URL. One is running elsewhere.

Generally this happens with a development or test instance created by a data export, and the mail functionalities were not disabled in that instance, as explained in the documentation Creating a test environment for Jira.

Resolution

    -Datlassian.mail.fetchdisabled=true -Datlassian.mail.senddisabled=true