Incoming Mail Handler: ERROR SerivceRunner atlassian.mail.incoming.mailfetcherservice

Receiving the following message in the logs. In fact we receive so many that the logs will fill up, filling up the filesystem then halting the system if we don't stay on top of things.

2013-02-05 08:09:56,445 QuartzWorker-0 ERROR ServiceRunner    EmailAccount [atlassian.mail.incoming.mailfetcherservice] EmailAccount[10400]: Exception: null
javax.mail.FolderClosedException
    at com.sun.mail.imap.IMAPMessage.getProtocol(IMAPMessage.java:145)
    at com.sun.mail.imap.IMAPMessage.getHeader(IMAPMessage.java:743)
    at com.atlassian.jira.service.services.mail.MailFetcherService$MessageProviderImpl.getAndProcessMail(MailFetcherService.java:250)
    at com.atlassian.jira.service.services.mail.MailFetcherService.runImpl(MailFetcherService.java:349)
    at com.atlassian.jira.service.services.file.AbstractMessageHandlingService.run(AbstractMessageHandlingService.java:250)
    at com.atlassian.jira.service.JiraServiceContainerImpl.run(JiraServiceContainerImpl.java:61)
    at com.atlassian.jira.service.ServiceRunner.execute(ServiceRunner.java:47)
    at org.quartz.core.JobRunShell.run(JobRunShell.java:195)
    at com.atlassian.multitenant.quartz.MultiTenantThreadPool$MultiTenantRunnable.run(MultiTenantThreadPool.java:72)
    at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:520)

Removed and recreated the Incoming Mail Handler, reset the password for the email account. Tested within Jira with success. Still receiving the errors during the email parsing in the logs. Ran updates to plugins without errors.

Any assitance is greatly appreciated.

2 answers

1 accepted

Removed a field that wasn't really needed as required. Once this field was removed from the create screen, the mail fetcher started operating as expected.

Just curious: Which field?

On the "add" screen for this project, i made a field manditory (attachment). Although the error didn't state which field was the culprit, I was able to identify through process of elimination.

0 vote
Richie Gee Atlassian Team Feb 04, 2013

Hi there,

I have seen issues on this resolved by increasing the timeout period, can you try check if this resolved your problem.

Alternatively, you can check if your bulk forward email is set to deliver to the same folder that your mail handler process, this might be the one causing this. Set the bulk forward to another account or different folder see if this fixes your problem.

Hope this helps, cheers!

Thanks for you reply Richie.

After further digging I found a hint to go on, "Exception: null". This led me to investigate the "required" fields on the create screen for this project. Once I removed the field that wasn't really needed as required, messages started flowing properly.

Richie Gee Atlassian Team Feb 05, 2013

Hi Bob,

Glad to hear that you managed to resolve it locally and sharing out with the community :)

Thank you and have a great day ahead :)

Suggest an answer

Log in or Sign up to answer
How to earn badges on the Atlassian Community

How to earn badges on the Atlassian Community

Badges are a great way to show off community activity, whether you’re a newbie or a Champion.

Learn more
Community showcase
Posted Thursday in Off-topic

Friday Fun: Magic Eyes

...staring into the background. Once the image pops out in 3D, you can look around the picture and enjoy. If you will see if you are a true illusion master! :) You did it? :) Wow! Awesome! As a bonus...

414 views 79 11
Join discussion

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you