-
Suggestion
-
Resolution: Fixed
-
None
NOTE: This suggestion is for Confluence Server. Using Confluence Cloud? See the corresponding suggestion.
The current process for setting up a secure smtp connection is a joke.
The process is very simular for JIRA too:
http://confluence.atlassian.com/display/JIRA/Configuring+JIRA+to+Send+SMTP+Mail
The problem with the JIRA process is that it requests the user to move jars around in the archive we give them (on top of the config problems)!
I've attached a screenshot of setting up secure smtp in TeamCity - no xml editing, no downloading certificates, it's all done from the admin screen and works first go.
This is going to become more of a problem as more people move to Google Apps, as the gmail smtp server will only allow secure connections.
- duplicates
-
- Closed
- is duplicated by
-
- Closed
-
- Closed
- is related to
-
CONFSERVER-9541 SMTPS broken in atlassian-mail
-
- Closed
-
-
- Closed
-
- Closed
- relates to
-
- Closed
- mentioned in
-
Page Loading...
-
-
-
-
-
-
-
-
-
[CONFSERVER-18770] Make configuring SMTP with SSL easier
Since my ISP (Comcast) blocked outgoing connections on port 25 (default unsecure SMTP) I am needing to change to a different port for SSL. Since this isn't supported straight out, I need to configure a JNDI for connecting to a SSL SMTP. So far I have not yet done it successfully. I've wasted 6+ hours on this. Still, i'm without email notifications. PLEASE ATLASSIAN, MAKE THIS EASY!
Giovanni Silva
added a comment - The configuration on server.conf is really tedious. Every time I upgrade my system I take 25 minutes instead of 2, this is because I have to stop the confluence instance again after upgrade and redo every custom configuration.
The most annoying thing a have to do (so annoying that I keep my instance out of date and wait some updates until the upgrade worthwhile) is:
1. Stop confluence. Again (this take time on my system)
2. Move (don't copy) activation-1.0.2.jar and mail-1.4.1.jar from <confluence-install>/confluence/WEB-INF/lib to <confluence-install>/lib.
(Are you seriously? Why a have to do that? And why the confluence package don't do that by default? Some freak bug like some microsoft products? Just kidding )
3. I'm smart so I don't type again the configuration on server.xml, I make a copy, but I cannot ensure that my copy just change the lines for mail config and I have to make a diff on the command line to be sure that I will not break the system and have to stop confluence again.
Not least but important too. I have to take care of the security of that file, if someone read that content my account is compromised. Well my system is secured and only root has access but who knows, and what about shared servers that others can be using, like universities?
Jira have a configuration for SMTP SSL email, and this is not broken between upgrades because is in the database.
This is easy to implement in spring config. So be nice with me and other sys devs.
By the way, I have other configurations like SSO with Crowd. Is tedius too, every config that depends on files and cannot be automatic created by confluence (and jira, and stash, and crowd) is tedius to maintain between upgrades.
Keep all on database and make the upgrade a easy, funny and routine part of your products
Giovanni Silva
added a comment - The configuration on server.conf is really tedious. Every time I upgrade my system I take 25 minutes instead of 2, this is because I have to stop the confluence instance again after upgrade and redo every custom configuration.
The most annoying thing a have to do (so annoying that I keep my instance out of date and wait some updates until the upgrade worthwhile) is:
1. Stop confluence. Again (this take time on my system)
2. Move (don't copy) activation-1.0.2.jar and mail-1.4.1.jar from <confluence-install>/confluence/WEB-INF/lib to <confluence-install>/lib.
(Are you seriously? Why a have to do that? And why the confluence package don't do that by default? Some freak bug like some microsoft products? Just kidding )
3. I'm smart so I don't type again the configuration on server.xml, I make a copy, but I cannot ensure that my copy just change the lines for mail config and I have to make a diff on the command line to be sure that I will not break the system and have to stop confluence again.
Not least but important too. I have to take care of the security of that file, if someone read that content my account is compromised. Well my system is secured and only root has access but who knows, and what about shared servers that others can be using, like universities?
Jira have a configuration for SMTP SSL email, and this is not broken between upgrades because is in the database.
This is easy to implement in spring config. So be nice with me and other sys devs.
By the way, I have other configurations like SSO with Crowd. Is tedius too, every config that depends on files and cannot be automatic created by confluence (and jira, and stash, and crowd) is tedius to maintain between upgrades.
Keep all on database and make the upgrade a easy, funny and routine part of your products There are two existing issues related to this: CONF-9541 (bug), CONF-12111 (task).
You might want to close the others, or this one.
Customer comment:
Andy,
Thank you for the examples and information, but we're interested in configuring Confluence, not writing a custom Java application to send mail.
Why cant the Jira email set up be ported to this? It is so much better.. Its like the code has already been written just needs to be converted for Confluence?