PutEmail processor SSLHandshakeException while sending email using Gmail SMTP

[#1]

I have been trying to send an email via NiFi using PutEmail processor with Gmail/Outlook both and getting same exception in both of the configuration as 

PutEmail[id=3611dcb8-0183-1000-8a1d-df8f12f92438] Failed to send email for StandardFlowFileRecord[uuid=017c80a8-fad0-493b-a427-fa72b9a530c7,claim=StandardContentClaim [resourceClaim=StandardResourceClaim[id=1663081396353-45, container=default, section=45], offset=521106, length=538],offset=0,name=f37f23a1-e328-4eff-bb30-6f125369ebf7,size=538]: Could not convert socket to TLS; routing to failure: javax.mail.MessagingException: Could not convert socket to TLS;
  nested exception is:
	javax.net.ssl.SSLHandshakeException: No appropriate protocol (protocol is disabled or cipher suites are inappropriate)

The configuration is set as below : 

Current NiFi version is  : 1.13.2

Java Version : 
openjdk version "11.0.16" 2022-07-19
OpenJDK Runtime Environment (build 11.0.16+8-post-Ubuntu-0ubuntu120.04)
OpenJDK 64-Bit Server VM (build 11.0.16+8-post-Ubuntu-0ubuntu120.04, mixed mode sharing)

Kindly provide any guidance to resolve this issue.

[#2 · Accepted solution]

@PratikParekh 

The putEmail processor supports the adding of dynamic configuration properties as outlined in the linked documentation.  
https://javaee.github.io/javamail/docs/api/com/sun/mail/smtp/package-summary.html

It would be helpful to collect the full stack trace written to the nifi-app.log rather then sharing the partial shown via the processor bulletin produced on the NiFi UI. From that stack trace output you may be able to determine what dynamic properties need to be added.

If you found that the provided solution(s) assisted you with your query, please take a moment to login and click Accept as Solution below each response that helped.

Thank you,

Matt

[#3]

Hi @PratikParekh, Has the reply helped resolve your issue? If so, please mark the appropriate reply as the solution, as it will make it easier for others to find the answer in the future.

[#4]

This has been resolved by upgrading NiFi to version 1.15 and above. Below this version not supporting TLS configuration.