portal entry

select a category, or use search below
(searches all categories and all time range)
Title:

CFMAIL on port 587 Issues!

| View in Portal
November 06, 2019 12:14:11 AM GMT
1 Comment
<p>How do we make the mail run on port 587 without getting errors?</p>
<p>The post <a rel="nofollow" href="https://coldfusion.adobe.com/2019/11/cfmail-port-587-issues/">CFMAIL on port 587 Issues!</a> appeared first on <a rel="nofollow" href="https://coldfusion.adobe.com">ColdFusion</a>.</p>
Labels: ColdFusion 2016, Question, Windows 2016 Support, cfmail, coldfusion 2016, question, windows 2016 support

Comments:

There can be many explanations for what's amiss, but I will offer two that are rather common for ssl-related issues in CF, and then close with a couple other possibilities. <strong>First</strong>, you say you imported a cert using keytool. Ok, but let's talk about WHERE you put that cert. Note that you need to put it in the /lib/security/cacerts of wherever cf is naming its jvm to be. And that may not be the jre folder under the cf folder, though many resources show (including from Adobe) will presume to show using the keytool to put a cert there. The thing is, if someone may have changed cf since installation to use a new jvm, then your cf admin jvm page will show it pointing elsewhere, and you need to import the cert into the /lib/security/cacerts of THAT folder instead. And when you may change jvm’s in the future, don’t forget to bring the certs along, though only if still needed. See my next point. <strong>Second</strong> and speaking of changing the jvm, somemes such a cert import is NOT needed after all, to fix ssl-related problems. You may simply need to update the jvm that cf is using. For more, see my post: <a href="https://coldfusion.adobe.com/2019/06/error-calling-cf-via-https-solved-updating-jvm/">https://coldfusion.adobe.com/2019/06/error-calling-cf-via-https-solved-updating-jvm/</a> Indeed, some folks have been importing certs over and over as they DID move to new jvm’s (see above) when in fact the cert was no longer really needed. Hope that’s helpful. Let us know if you resolve things or not. If not, then consider finally the possibility of conflicts on that port 587 either from a firewall or anti-virus tool. And then do clarify whether those messages above were all from when things were configured one way or another. If from when configured one way, are they different when things are configured another?
Comment by Charlie Arehart
2511 | November 06, 2019 01:16:22 PM GMT