![360works email configuration default 360works email configuration default](https://www.motobit.com/help/emailexport/img/outlook-menu-tools-accounts.gif)
AMS360 supports your efforts to retain more business. Higher client retention rates and agency growth go hand-in-hand.
360WORKS EMAIL CONFIGURATION DEFAULT CODE
Here is some example Java code that illustrates the problem. Since this works with Apache on the server, it seems to me that I should be able to make some sort of configuration change on the server to also work with Tomcat, without needing to change the Java clients.
360WORKS EMAIL CONFIGURATION DEFAULT UPDATE
However, this is not a practical solution, because I cannot release an update at this time for our Java clients.
![360works email configuration default 360works email configuration default](https://i.ytimg.com/vi/ECBJufSADb8/maxresdefault.jpg)
I have gotten this to work by forcing the Java client to use the TLSv1 protocol (-Dhttps.protocols=TLSv1).
![360works email configuration default 360works email configuration default](https://docs.bamboosolutions.com/wp-content/uploads/2017/06/HW14_Mail_Client_Form.png)
In addition, non-Java code (like curl) can connect to the Tomcat SSL connection. However, the exact same Java code can connect to the same server on a different port hosted by Apache with SSL. I can make changes to the server, but not to the existing Java client.įor some reason, whenever a Java client connects to the Tomcat server using SSL, it is not able to connect - the connection is reset by the server. I am trying to use SSL with Tomcat and an APR connector.