Disable mail services after xml restore of JIRA backup to another instance

Many peoples get themselves into "bizarre" problems, when they restore a xml backup of the production into a test JIRA instance and start to receive "weird" emails.

Users create support request in SAC and blame JIRA for:

• notification emails on "ghost"/not existing issues,
• duplicated notification and subscription messages,
• outdated content of the subscription messages.

Quotes from SAC cases:

For instance, if I send an email to help@mycomp.com it will create a ticket in jira... sometimes it will create it as TS-5769 (The proper ticket number), and other times it would be TS-5716 (an outdated ticket). The email that we receive as a notification stating the ticket was created seems fine, it has all the information that was submitted (except for the ticket number), but when you click on the link (ticket number), it will be an outdated ticket.... It's very strange!

and one more about subscription:

One of our users had a subscription set up that she had deleted, along with the filter used for the subscription, so both of these no longer exist. The subscription is still being sent on the schedule she had set up, and it's always the same old data. I posted a message on the forum but their ideas have not worked. Can anyone help me with this? I don't think there has been any info in the log on it, but I'll attach those just in case, along with one of the email subscriptions that was just sent last night.

Perhaps JIRA should:

• on the Import page give option to manually enable the services after the restore, but by default disable them,
• after restore list all disabled services,
• display warning in the UI that services are disabled,
• allow to manually enable the single services from the UI.