Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Mailserver Connection | How to automate an hourly or daily test of this connection

Dirk Tramberend
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
June 17, 2020

Hi,

I'm familiar with how to connect JIRA to the mailserver, and where to find connectivity logs, and how to manually test the connection per Settings > Products > Email Requests > Actions > Test.

I just wonder how I can establish an automated routine to test the connection once or twice a day and then notify me in case of trouble.

Thanks, Dirk

1 answer

1 accepted

0 votes
Answer accepted
Daniel Ebers
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
July 6, 2020

Hi Dirk,

this differs a bit depending on if you generally want to find out is the mailserver is up and running or if you aim to do end-to-end-tests as for mail (f.e. sending test mails through the server to really make sure everything is okay).

Checking the mailserver's general availablibity (port open?) is a common scenario which I see to be done outside Jira to be honest. Monitoring tools like Icinga (or similar) should fulfill this requirement.

Make sure you plan on how to be notified if a mail server malfunction is identified as the mail server in that case would most probably not be able to inform you in such cases.

In case you plan to do a end-to-end approach you would have to send a test mail on regular basis to a mailbox and test if it was delivered. For this approach the same applies: you would have to ensure you are notified about any malfunction by a different implementation than the current failing mail server.

Cheers,
Daniel

Dirk Tramberend
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
July 6, 2020

Thanks Daniel. Will consider this. Found in the meantime that all our recent connectivity issues had a common pattern in the Email Connectivity Log: The absence of a daily Status=CONNECT log entry, accompanied by frequent Status=FAILURE log entries, mostly indicating that "email pulling" had failed. Or with other words: As long as I see a daily Status=CONNECT entry without any such Status=FAILURE entries, we're good. Manually checking this log on a daily basis is not yet the automatism I'm looking for, however it works. Regards, Dirk

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
PERMISSIONS LEVEL
Product Admin
TAGS
AUG Leaders

Atlassian Community Events