Skip to main content
Solved

Emailer fails with SSL exception

lifalin2016
Contributor
Forum|alt.badge.img+29

Hi all.

Our IT department has recently moved our mail system to Office365, and so all the emails sent from FME must now use a new endpoint and credentials.

I've tried to run a super simple workspace, and it fails: Emailer_Søgeord: <class 'ssl.SSLError'>: [SSL: WRONG_VERSION_NUMBER] wrong version number (_ssl.c:1076)

Our previous setup didn't use SSL, but the new one does. But apparently FME cannot handle it ?

The only items changed are: host, port, encryption (from None to SSL), and sender's username and password.

Using FME 2020.0 and Python 3.7+, and I have upgraded the Emailer transformer from 2017 to the latest.

Please advice. Cheers.

Best answer by lifalin2016

Ok. my digging did uncover the cause. It is indeed the encryption, that now has to be TLS, not SSL.

It seems that this was changed in Python 3.5, and since 2020.0 doesn't support any older versions (except for 2.7 if installed), TLS is the new default.

My last obstacle was my weary butter fingers, that misspelled "relay" as "reply" in the credentials setup. After that was corrected, the email was sent correctly.

View original
-- Cheers, Lars I.
Did this help you find an answer to your question?

5 replies

david_r
Celebrity
  • david_rCelebrity
  • April 14, 2020

It may be a long shot, but have you tried different ways of entering the mail server hostname, trying both with and without the https prefix in the Emailer:

smtp.office365.com

https://smtp.office365.com

Of course you'll have to use the proper hostnames, the above are just examples.

lifalin2016
Contributor
Forum|alt.badge.img+29
  • lifalin2016Contributor
  • Author
  • Contributor
  • April 14, 2020
david_r wrote:

It may be a long shot, but have you tried different ways of entering the mail server hostname, trying both with and without the https prefix in the Emailer:

smtp.office365.com

https://smtp.office365.com

Of course you'll have to use the proper hostnames, the above are just examples.

Isn't https and SSL synonymous ?

Besides, the error message talks about a version number issue, not a protocol issue.

-- Cheers, Lars I.
david_r
Celebrity
  • david_rCelebrity
  • April 14, 2020
lifalin2016 wrote:

Isn't https and SSL synonymous ?

Besides, the error message talks about a version number issue, not a protocol issue.

To a human, yes :-)

lifalin2016
Contributor
Forum|alt.badge.img+29
  • lifalin2016Contributor
  • Author
  • Contributor
  • April 14, 2020

I've googled the error message, and it seems it might have to do with the protocol version having changed from PROTOCOL_SSLv3 to PROTOCOL_TLS in Python 3.5.

I tried to change the encryption in the Emailer to TLS (instead of SSL), but that only gave me another error:

SMTPDataError: Could not complete request. Message: (554, b'5.2.0 STOREDRV.Submission.Exception:SendAsDeniedException.MapiExceptionSendAsDenied; Failed to process message due to a permanent exception with message Cannot submit message. 0.35250:5B2C0000, .... [Hostname=VI1P190MB0542.EURP190.PROD.OUTLOOK.COM]')

Digging deeper.

-- Cheers, Lars I.
lifalin2016
Contributor
Forum|alt.badge.img+29
  • lifalin2016Contributor
  • Author
  • Contributor
  • Best Answer
  • April 14, 2020

Ok. my digging did uncover the cause. It is indeed the encryption, that now has to be TLS, not SSL.

It seems that this was changed in Python 3.5, and since 2020.0 doesn't support any older versions (except for 2.7 if installed), TLS is the new default.

My last obstacle was my weary butter fingers, that misspelled "relay" as "reply" in the credentials setup. After that was corrected, the email was sent correctly.

-- Cheers, Lars I.

Reply


Helpful Members This Week

Community Stats

31,228
Posts
118,416
Replies
38,827
Members

Latest FME

Terms & ConditionsCookie settings

Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings
A product of
Safe Software respectfully acknowledges that we live, learn and work on the traditional and unceded territories of the Kwantlen, Katzie, and Semiahmoo First Nations.