Mail not leaving mail queue after reindex

[sachin]

Showing below message in mail queue

using jira software 7.0

This page shows you the current JIRA internal event queue, whose events may trigger notification emails.

The queue currently has 645 items in it. The mail queue is currently sending. Bypass currently sending mail - Push sending of current mail to the background, to let others through. Mail details will be logged for debugging. Flush mail queue - this will send all mail in the queue immediately.

[Tom Lister]

Hi

It's not unusual to see tickets in the queue. You can look at the timestamps to see if its building up constantly and not clearing

There are links to troubleshooting tips here

https://community.atlassian.com/t5/Jira-Software-questions/Mail-not-leaving-mail-queue-after-reindex/qaq-p/1075901

On our system we had an issue with a large number of mail handlers configured to run at the same time. When we change the scheduling to move them a minute or two apart we got much better throughput.

Tom

[sachin]

Thanks tom for your reference ,..i have restart jira service now .

now 

JIRA does not create issue by email for JIRA users some mail is got stuck in gmail not create a issue in jira .Please help on this issue 

[Tom Lister]

Hi

check your Jira-Atlassian.log files

outside of service management users need permission to create tickets in a project 

you should see log entries that show permission errors

[sachin]

ok i will check the logs file and how can i give the permission to user .Please guide me it will be help full

[Tom Lister]

Hi @sachin 

There is more information on email handlers at the links below.

https://confluence.atlassian.com/adminjiraserver/creating-issues-and-comments-from-email-938847641.html

https://support.atlassian.com/jira-cloud-administration/docs/create-issues-and-comments-from-email/

For an email sender to create a ticket the from email must match a Jira user and that user needs to be added to a project role that can create tickets.

If you don't want to add users to Jira then you can configure the email handler to use a default reporter - usually set as a dummy internal user account to make it more obvious. Or you can add a 'forward email' where failed incoming messages can be sent.

Tom