Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Incoming Mail Handler issue


I send a bottle in the sea because I don't know why I have this issue and how to fix it.

Since several days, we have a problem to create tickets from mail handler.
Previously we set up mail handler on test platform to validate a new jira project.
We set up on test platfom the mail puller periodicity every minutes.
After our test, we remove mail handler from test platform and recreate it on our production platform.

After several weeks , we started to have mail handler issues (no ticket creation).
After investigating, we changed the mail handler periodicity from 1 minutes to 30 minutes on production platform and it worked.

But since several days, ticket creation failed with these errors (see attached file).

It seems that our test platform still to try to handle mails wherease:
- we remove mail server settings on test platform
- we remove mail handler on test platform
- we delete the ticket MHT-34654 on test platform
- we restart production platform
- we restart test platform

But we still have this error on the production server logs.
For the moment, we deactivate mail processor and email puller on test plaftorm.

In addition we turned off the test platform and we still have issue and it's already trace in log whereas the test platform was off.

So I conclude the problem comes from the production instance.

Thank you

Server Platform Jira Core 7.8.3

Here the log error:


2020-03-27 12:46:36,824 ERROR [Mr Help Mail Handler] Caesium-1-1 anonymous Mr Help Handler Mr Help Handler[10400]: The connection is no longer open, messages marked as deleted will not be purged from the remote server: until the next run.
2020-03-27 13:06:48,113 INFO [Mr Help Mail Handler] Caesium-1-4 Mr Help Handler Received message with another JIRA instance's fingerprint: Vallourec - (MHT-34654) Documentation and Web
2020-03-27 13:18:36,531 ERROR [Mr Help Mail Handler] Caesium-1-4 anonymous Mr Help Handler Mr Help Handler[10400]: The folder has been closed on us, stop processing any more emails: null
at javax.mail.internet.MimeBodyPart.getContent( [javax.mail-1.5.6.jar:1.5.6]
at com.metainf.jira.plugin.emailissue.handler.RichTextMailUtils.extractTextFromPart( [?:?]
at com.metainf.jira.plugin.emailissue.handler.RichTextMailUtils.getBodyFromMultipart( [?:?]
at com.metainf.jira.plugin.emailissue.handler.RichTextMailUtils.getBodyFromMultipart( [?:?]
at com.metainf.jira.plugin.emailissue.handler.RichTextMailUtils.getRichTextContent( [?:?]
at com.metainf.jira.plugin.emailissue.mail.EmailBean.<init>( [?:?]
at com.metainf.jira.plugin.emailissue.handler.IssueSupportingMessageHandlerContext.<init>( [?:?]
at com.metainf.jira.plugin.emailissue.handler.IssueSupportingMessageHandlerContext.<init>( [?:?]
at com.metainf.jira.plugin.emailissue.handler.EmailThisIssueMailHandler.handleMessage( [?:?]
at$1.process( [jira-api-7.3.8.jar:?]
at$MessageProviderImpl.getAndProcessMail( [jira-api-7.3.8.jar:?]
at [jira-api-7.3.8.jar:?]
at [jira-api-7.3.8.jar:?]
at [classes/:?]
at com.atlassian.jira.service.ServiceRunner.runService( [classes/:?]
at com.atlassian.jira.service.ServiceRunner.runServiceId( [classes/:?]
at com.atlassian.jira.service.ServiceRunner.runJob( [classes/:?]
at com.atlassian.scheduler.core.JobLauncher.runJob( [atlassian-scheduler-core-1.7.0.jar:?]
at com.atlassian.scheduler.core.JobLauncher.launchAndBuildResponse( [atlassian-scheduler-core-1.7.0.jar:?]
at com.atlassian.scheduler.core.JobLauncher.launch( [atlassian-scheduler-core-1.7.0.jar:?]
at com.atlassian.scheduler.caesium.impl.CaesiumSchedulerService.launchJob( [atlassian-scheduler-caesium-1.3.3.jar:?]
at com.atlassian.scheduler.caesium.impl.CaesiumSchedulerService.executeClusteredJob( [atlassian-scheduler-caesium-1.3.3.jar:?]
at com.atlassian.scheduler.caesium.impl.CaesiumSchedulerService.executeClusteredJobWithRecoveryGuard( [atlassian-scheduler-caesium-1.3.3.jar:?]
at com.atlassian.scheduler.caesium.impl.CaesiumSchedulerService.executeQueuedJob( [atlassian-scheduler-caesium-1.3.3.jar:?]
at com.atlassian.scheduler.caesium.impl.CaesiumSchedulerService$1.consume( [atlassian-scheduler-caesium-1.3.3.jar:?]
at com.atlassian.scheduler.caesium.impl.CaesiumSchedulerService$1.consume( [atlassian-scheduler-caesium-1.3.3.jar:?]
at com.atlassian.scheduler.caesium.impl.SchedulerQueueWorker.executeJob( [atlassian-scheduler-caesium-1.3.3.jar:?]
at com.atlassian.scheduler.caesium.impl.SchedulerQueueWorker.executeNextJob( [atlassian-scheduler-caesium-1.3.3.jar:?]
at [atlassian-scheduler-caesium-1.3.3.jar:?]
at [?:1.8.0_102]
2020-03-27 13:18:36,626 ERROR [Mr Help Mail Handler] Caesium-1-4 anonymous Mr Help Handler Mr Help Handler[10400]: The connection is no longer open, messages marked as deleted will not be purged from the remote server: until the next run.

0 answers

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events