We checked our configuration in the LabKey Tomcat context /data/tomcat/conf/Catalina/localhost/ROOT.xml. All the parameters are correct/unchanged.

Does your configuration specify the "mail.smtp.ssl.enable" or "mail.smtp.starttls.enable" properties? We did make a minor change in 11.2 to improve support for these modes.

Adam

The configuration for "mail.smtp.starttls.enable" is true.

So you're enabling TLS but not specifying a password? I wasn't aware that was a valid combination, but apparently it is. If you can't work around the problem (e.g., by removing the TLS setting or adding a password) then this will require a hotfix to 11.2. Sorry for the inconvenience.

We did set a password. :) We are not sure exactly what the cause of the problem is. Are we the only people that run into this after the upgrade.

Thanks, Adam!

No one else has reported problems, but there are a lot of ways to configure SMTP and the JavaMail documentation is not at all clear on best practices to support every configuration.

Would you mind emailing me your "mail/Session" Resource from ROOT.xml? Just xxxx out any passwords first.

Thanks,
Adam

Hi Maya,

I find it interesting that you didn't have problems with email sending prior to 11.2 since you use tls. (Since I was unable to get it working without the latest change, having tried various resource combinations).

This is our resource that works:

<Resource name="mail/Session" auth="Container"
       type="javax.mail.Session"
       mail.smtp.host="mail.example.com"
       mail.smtp.user="xxxxx"
       mail.smtp.password="xxxxx"
       mail.smtp.port="587"
       mail.smtp.auth="true"
       mail.smtp.starttls.enable="true"/>

Thanks, Trent. Our Resource definition is as follows:

<Resource name="mail/Session" auth="Container" type="javax.mail.Session" password="xxxx"       mail.debug="false"       mail.smtp.user="xxxx"       mail.smtp.host="smtp.washington.edu"       mail.smtp.auth="true"       mail.smtp.port="465"       mail.smtp.starttls.enable="true"       mail.smtp.socketFactory.class="javax.net.ssl.SSLSocketFactory"       description="email resource"   />

Our System Admin tried the setting on a local tomcat with a new java.mail package. The setting only worked when he changed mail.smtp.user to mail.user. Unfortunately, the latter setting didn't work on the LabKey server.

This problem only seemed to have propped up after we upgraded to the new server. The setting worked for the last version.

Thanks to Brian. The problem has been resolved. :)

For documentation sake, I wanted to post what fixed the problem. Following @trent's recommendation and the documentation, we changed the Resource to be

<Resource name="mail/Session" auth="Container"
       type="javax.mail.Session"
       mail.debug="false"
       mail.smtp.host="smtp.washington.edu"
       mail.smtp.user="xxxxx"
       mail.smtp.password="xxxxx"
       mail.smtp.port="465"
       mail.smtp.auth="true"
       mail.smtp.starttls.enable="true"
       mail.smtp.socketFactory.class="javax.net.ssl.SSLSocketFactory"
       description="email resource"/>

After a restart of the LabKey Server, email was working.