FishEye/Crucible e-mail test failing Edited

[David Rosenfeld]

I have installed a FishEye/Crucible instance in AWS, running on Amazon Linux, with a Postgres database.  I also have Jira and Confluence servers in this same environment, and their e-mail (with these same parameters) works with no problems.

The FE/C version is Version:4.5.3 Build:20180321104931 2018-03-21

The e-mail settings look like this:

SMTP host name: email-smtp.us-east-1.amazonaws.com
SMTP port: 465
Use SSL/TLS: True
Username: xxxxxxxxxxxxxxxxxxxxxxxxxx
Password: zzzzzzzzzzzzzzzzzzzzzzzz
Connection timeout: 30
Timeout: 30

If I have no timeouts, the system will spin until I get a timeout page from Nginx (which is my reverse proxy server).  With the timeouts set to 30 (as shown above), and logging enabled, I get this trace:

Starting mail system...
mail.smtp.host = email-smtp.us-east-1.amazonaws.com
mail.smtp.starttls.enable = true
mail.smtp.port = 465
mail.from = crucible@mycompany.com
mail.smtp.connectiontimeout = 30000
mail.smtp.timeout = 30000
mail.smtp.auth = true
username = xxxxxxxxxxxxxxxxxxxx
password = *******
Mail system started.
Using from address: 'crucible@mycompany.com'
DEBUG: getProvider() returning javax.mail.Provider[TRANSPORT,smtp,com.sun.mail.smtp.SMTPTransport,Sun Microsystems, Inc]
DEBUG SMTP: useEhlo true, useAuth true
DEBUG SMTP: useEhlo true, useAuth true
DEBUG SMTP: trying to connect to host "email-smtp.us-east-1.amazonaws.com", port 465, isSSL false
DEBUG SMTP: exception reading response: java.net.SocketTimeoutException: Read timed out
problem sending email
Read timed out
at java.net.SocketInputStream.socketRead0(Native Method)
at java.net.SocketInputStream.socketRead(SocketInputStream.java:116)
at java.net.SocketInputStream.read(SocketInputStream.java:171)
at java.net.SocketInputStream.read(SocketInputStream.java:141)
at com.sun.mail.util.TraceInputStream.read(TraceInputStream.java:97)

Note that it shows "isSSL False", even with the "Use SSL/TLS" parameter set to "True".  I think this is the cause of the failure, because AWS SES e-mail requires secure SMTP, but I don't know how to fix it.  It appears that the value I'm setting with the radio button is being ignored.

[Caterina Curti · Accepted solution]

Hi @David Rosenfeld,

It looks like you may be running into this known issue:

- FE-3912: Fisheye mail doesn't work with SMTPS

The bug report above also contains a workaround that you could try.

Cheers,

Caterina - Atlassian