JIRA mail server settings in Confluence et al

After fighting with mail server configuration for months, I tried using JIRA's option to connect to Gmail, and amazingly it worked right out of the box, with nothing required on the server.

However I am unable to set up SMTP servers the same way for Confluence, FishEye, Bamboo or Stash. All of them time out and fail to send a test message with various errors. Confluence gets the proxy error below, for example, even though the settings are the same (as much as possible, given the limited fields Confluence provides).

How does one resolve the differences in mail server setup options between tools and get them all to work like JIRA? Or if possible, is it possible to share a single JNDI configuration between all tools?

2 answers

1 accepted

How does one resolve the differences in mail server setup options between tools and get them all to work like JIRA? Or if possible, is it possible to share a single JNDI configuration between all tools?

I guess this is because each application has different architecture and were different in design. I don't think it's possible to share a single JNDI though. JIRA uses java:comp/env/mail/GmailSmtpServer for its JNDI location while Confluence uses java:comp/env/mail/Session.

I had many times configuring Confluence to use GMail as the mail server using the following documentation and it works like a charm: https://confluence.atlassian.com/display/CONFKB/How+do+I+configure+Confluence+to+use+GMail+as+the+mail+server

The screen shot indicates that there could be an issue with the proxy configuration. You can try to check if the mail server is working properly when the proxy is bypassed and Confluence is accessed directly through localhost/IP. You might also want to double check on the proxy setting against this documentation: https://confluence.atlassian.com/display/DOC/Running+Confluence+behind+Apache

I never really got this working, but this sounds about right. I think there is a proxy thing going on behind the scenes, but I still wonder why JIRA is able to work around it so easily, and every other Atlassian product seems to have its own mess of configuration.

You have to move a couple of jars from WEB-INF/lib to installation-dir/lib. I believe is something related to activationxxx.jar and mailxxx.jar

Interestingly, I didn't have to move those files out of WEB_INF for JIRA, and moving them for Confluence (and restarting) doesn't help, unfortunately.

Oh no, I mean to say move those files in the same JIRA instance(WEB-INF/lib) to (JIRA/lib).

No confluence involved here.

Check this here https://confluence.atlassian.com/display/JIRA/Using+Gmail+as+a+JIRA+Mail+Server

Sorry, I could have been a bit clearer. JIRA email is working fine, no problems there. I'm wondering why it is so easy to set up, and yet every other program (Confluence, FishEye, Bamboo, Stash) refuse to work. Thus it's interesting that I didn't have to move those JARs for JIRA, and suggests something else is to blame.

Suggest an answer

Log in or Join to answer
Community showcase
Sarah Schuster
Posted Jan 29, 2018 in Jira

What are common themes you've seen across successful & failed Jira Software implementations?

Hey everyone! My name is Sarah Schuster, and I'm a Customer Success Manager in Atlassian specializing in Jira Software Cloud. Over the next few weeks I will be posting discussion topics (8 total) to ...

2,798 views 11 18
Join discussion

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