It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Improvement: Mail Queue Service Delay

Brant Messenger Nov 05, 2013

Within the administration gui under outgoing mail when setting up an SMTP mail server, an input field should be added to allow us (administrators) to determine the amount of delay in seconds. Zero (0) would mean no delay send when event is created. One (1) or greater would delay the mail for that duration.

Personally, I do not want a delay at all.

1 answer

0 votes
Richie Gee Atlassian Team Nov 05, 2013

Hi Brant,

The mail queue flushing delay can be configured under the services, but the lowest poll is 1 minute. From what I understand as well, flushing every single second is a bad idea as the previous session might not even ended and JIRA starts to send again, might cause a lot of problem in the future. For my personal opinion, 1 minute is acceptable delay.

Hope this clarifies.

Brant Messenger Nov 05, 2013

Found the setting unders services, thank you.

All smtp servers will automatically queue the emails at its own interval.

When sending emails to an SMTP server an option should be allowed to bypass queuing in the application layer if the value is set to zero (0). Example: If (delay > 0) include delay else send now.

Brant Messenger Nov 11, 2013

Please define "might cause a lot of problem in the future". My personal opinion is stated in my improvement request. I will not close this issue until a direct answer is set. Either you won't improve jira or you will add to your improvement list?

Brant Messenger May 13, 2014

Admins need a way to NOT QUEUE EMAILS so that the SMTP server, Jira is connecting to, will handle that queuing for the system. Resulting in "Email Queue" issues being eliminated.

Russ Frizzell Aug 05, 2014

One improvement that could be made is to allow the poll time to be in seconds and then the mail queue service could simply check if a mail queue process is still running when it kicks off. If so, it does not spawn another process and waits until the next poll. If the age of the running instance is larger than a particular (maybe configurable) value, then it could kill the running process and re-run.

That could provide JIRA admins the option of lowering polling rates.

Suggest an answer

Log in or Sign up to answer
This widget could not be displayed.
This widget could not be displayed.
Community showcase
Published in Jira

Try Jira Cloud for Outlook: Organize your work without leaving your inbox

Hi Atlassian community, My name is Max and I work on the product integration team at Atlassian. I am pleased to announce the early access program for the Jira Cloud add-in for Outlook. This add-in...

1,507 views 3 14
Read article

Community Events

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

Find an event

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

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you