Service Desk: IMAP-Message rejected? Edited

Jira Version 7.3.7

ServiceDesk Version: 3.5.1

 

We are all of a sudden unable to fetch IMAP Mails:

 

We have round about 50 Mails in the support-INBOX and get always those 6  Lines:

2017-07-20 15:16:38,590 Caesium-1-2 ERROR ServiceRunner [c.a.m.incoming.jepp.puller] Messaging Error when MailPullerWorker pulls emails from support@obfuscated: Failed to load IMAP envelope
2017-07-20 15:17:00,388 Caesium-1-3 INFO anonymous Incomming [c.a.mail.incoming.mailfetcherservice] Incomming[10100]: Cannot handle message as the recipient(s) (jira@linux.local) do not match the catch email jira@netitwork.net
2017-07-20 15:17:00,695 Caesium-1-3 WARN anonymous Incomming [c.a.mail.incoming.mailfetcherservice] Incomming[10100]: Sender is anonymous, no default reporter specified and creating users is set to false (or external user management is enabled). Message rejected.
2017-07-20 15:17:01,003 Caesium-1-3 WARN anonymous Incomming [c.a.mail.incoming.mailfetcherservice] Incomming[10100]: Sender is anonymous, no default reporter specified and creating users is set to false (or external user management is enabled). Message rejected.
2017-07-20 15:17:01,309 Caesium-1-3 WARN anonymous Incomming [c.a.mail.incoming.mailfetcherservice] Incomming[10100]: Sender is anonymous, no default reporter specified and creating users is set to false (or external user management is enabled). Message rejected.
2017-07-20 15:17:01,619 Caesium-1-3 WARN anonymous Incomming [c.a.mail.incoming.mailfetcherservice] Incomming[10100]: Sender is anonymous, no default reporter specified and creating users is set to false (or external user management is enabled). Message rejected.

 

No more no less, what could be the issue? What can we provide to solve this issue?

1 answer

Hi Michael,

Based on what we see in the logs, I would start out with the knowledge base article titled Unable to create issue due to anonymous sender and no default reporter.  In order for the mail handler to create emails one of the following must be true:

  1. A default user. This is the reporterusername parameter.
  2. An existing user as the reporter.
  3. The parameter createusers set to true. If external user management is enabled, it must allow user creation.

Verify one of the above conditions are met if so the next step will be to enable debug logging.  Once you have done that, capture what the logs say and post the snippet around the time the issue was newly reproduced.

Cheers,

Branden

Suggest an answer

Log in or Join to answer
Community showcase
Teodora [Botron]
Published Thursday in Marketplace Apps

Jira Inferno: The Nine Circles of Jira Administration Hell

If you spend enough time as a Jira admin - whether you are managing a single, mid-sized instance, a large enterprise one or juggling multiple instances at once - you will eventually find yourself in ...

261 views 0 12
Read article

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
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot