Project

General

Profile

Bug #9118

Migrate FWD-SMTP-EMAIL to TLS1.2

Added by Galya B almost 2 years ago. Updated over 1 year ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Target version:
-
Start date:
Due date:
% Done:

100%

billable:
No
vendor_id:
GCD
case_num:
version_reported:
version_resolved:
reviewer:
production:
No
env_name:
topics:

History

#1 Updated by Galya B almost 2 years ago

TLS1 and TLS1.1 are not supported any more (disabled in newer javas in jdk.tls.disabledAlgorithms and not supported by mail servers like outlook). This issue presents itself by FWD-SMTP-EMAIL throwing javax.net.ssl.SSLHandshakeException: No appropriate protocol (protocol is disabled or cipher suites are inappropriate). The solution will require update to libraries and probably the code to make it work with TLS1.2.

#3 Updated by Greg Shah over 1 year ago

  • % Done changed from 0 to 100
  • Status changed from New to Test

I believe that 9360b (trunk rev 15665) has resolved this issue. Correct?

#4 Updated by Galya B over 1 year ago

Greg Shah wrote:

I believe that 9360b (trunk rev 15665) has resolved this issue. Correct?

I think so. Roger, if you can test this particular issue, you can close this task too.

#5 Updated by Roger Borrello over 1 year ago

Galya B wrote:

TLS1 and TLS1.1 are not supported any more (disabled in newer javas in jdk.tls.disabledAlgorithms and not supported by mail servers like outlook). This issue presents itself by FWD-SMTP-EMAIL throwing javax.net.ssl.SSLHandshakeException: No appropriate protocol (protocol is disabled or cipher suites are inappropriate). The solution will require update to libraries and probably the code to make it work with TLS1.2.

Hi Galya... does this present itself in a testcase? If not, the customer uses CREATE SMTP-EMAIL hMailer extensively in their code, so when #9360 is closed, this can be closed.

#6 Updated by Galya B over 1 year ago

Roger Borrello wrote:

Hi Galya... does this present itself in a testcase? If not, the customer uses CREATE SMTP-EMAIL hMailer extensively in their code, so when #9360 is closed, this can be closed.

It's not in testcases, but it is CREATE SMTP-EMAIL, so it's the same as the customer uses and can be closed with #9360.

#7 Updated by Roger Borrello over 1 year ago

Galya B wrote:

Roger Borrello wrote:

Hi Galya... does this present itself in a testcase? If not, the customer uses CREATE SMTP-EMAIL hMailer extensively in their code, so when #9360 is closed, this can be closed.

It's not in testcases, but it is CREATE SMTP-EMAIL, so it's the same as the customer uses and can be closed with #9360.

The customer said...

it worked with both unencrypted and encrypted mail server. With and without attachments. BEYOND THRILLED

So this should be closed.

#8 Updated by Greg Shah over 1 year ago

  • Status changed from Test to Closed

Also available in: Atom PDF