On Mon, December 21, 2020 20:00, Jaroslaw Rafa wrote:
>
> If you are able to connect via 465, then maybe the application just isn't
> designed to use "inline" TLS, but rather uses only SMTP-over-TLS? The latter
> is supported on port 465, while submission via port 587 requires first
> plaintext connection and then dynamic in-session switchover to TLS, using
> STARTTLS command. Maybe your application just does not support that?
That is a possibility. However, having looked at the example configurations
and discussions on the application support groups, it appears to me that
connecting to port 25 with STARTTLS is the accepted practice.
The problem I had with the certificate negotiation is not uncommon with this
application, due to Java's rather idiosyncratic PKI certificate handling. I had
reason to believe that when I finally solved that problem then everything else
would just work. The SSLv3 problem was a surprise, but was easily compensated
for. But, I still cannot get this application to send email so there must be
something else that I have done, or not done, which is preventing this from
working.
And it seems that I am past the SSL problems and into SMTP, I hope.
--
*** e-Mail is NOT a SECURE channel ***
Do NOT transmit sensitive data via e-Mail
Unencrypted messages have no legal claim to privacy
Do NOT open attachments nor follow links sent by e-Mail
James B. Byrne mailto:byrn...@harte-lyne.ca
Harte & Lyne Limited http://www.harte-lyne.ca
9 Brockley Drive vox: +1 905 561 1241
Hamilton, Ontario fax: +1 905 561 0757
Canada L8E 3C3
