Email puller disabled after using Maintenance Mode for Jira

Przemysław Boruta

Hello,

I've installed, enabled and activated "Maintenance Mode for Jira" plugin few days ago. Next, disabled the plugin using "Save and Disable - Button".
Today I've found, that my email puller stoped working, and jira reports it is "Disabled by system flag"

Mail fetching was disabled with the -Datlassian.mail.fetchdisabled=true or -Datlassian.mail.popdisabled=true JVM argument before JIRA was started. JIRA cannot fetch email until you remove the JVM argument and restart JIRA.

I've inspected my setenv.sh file, and found "DISABLE_NOTIFICATIONS" line is commented out. Despite that I can still find "jira.mail.fetch.disabled : true" in jira startup log.

Also tried disabling, removing, reinstalling etc. plugin from plugin manager - no luck here.

The only change I've made is installing and using plugin, as mentioned above.
Hoping for quick help from You.

Andy Heinzer

It's possible that the setenv file would not be used to define these startup arguments, but that only applies if you were running Jira on Windows and starting it as a service.  If that is the case, then take a look at Setting properties and options on startup.  It explains how you can set these kinds of startup options in the service settings in a different method.

If this doesn't help, please tell us

1. The version of Jira you are using
2. The operating system Jira is running on top of

Just for reference, the setenv.bat is used for Windows, and the setenv.sh is used for linux/unix installations.   Despite that fact both files will typically exist in both environments, it's just that you are unlikely to use one of them depending on your OS.

I don't believe the plugin is actually disabled with the button you mentioned.  The core functions might be removed, but Jira still would load up the code on startup if that plugin is enabled.   You could confirm that this plugin is not being loaded in Jira by

1. Stop Jira
2. go to $JIRAHOME/plugins/installed-plugins/ and then locate this plugin's .jar file and move it out of the $JIRAHOME directory
3. start jira again

This is one way to make sure that the plugin is not loading in some unexpected code.   If that still does not help, then I'd like to see if we can gather a support zip from your Jira to better troubleshoot this.