Service smtp - TLS/SSL support

lock
push_pin
done
Answered
2

Hi,

In version 8.0 service would accept smtp.office365.com port 587 with authentication in the smtp settings, however it seems now in 8.1 that this does not work anymore and the following error is given.

 

I've tried this on several installations and non of them work. Telnet from the server where NetServer for service is installed work fine to smtp.office365.com 587. 

I did some tries with gmail as well, and this work as long as port 465(SSL) is used, when trying port 587(TLS) for gmail smtp it gives the same error.

Is the TLS support gone from the smtp settings in service 8.1?

31 Oct 2017 | 12:00 AM

All Replies (2)

Hi Marius,

 

For office 365 you should not use SSL, so should try 587 without SSL

and second you should check what is your Default From address in the settings

system->settings->Default From address 

this should match User name in SMTP settings

 

maybe this will help 

31 Oct 2017 | 12:00 AM

Donatas is correct - for O365 you should not check the "Use SSL" .

I'll try to give some insight to why as FYI:

Most SMTP servers support encrypted connections form the start of the connection - Office365 does currently not, afaik.

- TLS uses STARTTLS - which upgrades the connection to an encrypted connection.

In Office365, it starts off with an unencrypted connection, and let's cURL know it supports STARTSTLS. This will make the connection upgrade to an encrypted connection.

EasyMail (before 8.1) did actually downgrade to a non-encrypted connection if the connection failed! We don't want that :) (that is why it worked before with EasyMail (before 8.1) - and do not with cURL (8.1)

- We want to be sure the connection is encrypted all the way if you have told so explicitly.

So - in scenarios where customers use Service and O365 - you may uncheck  "Use SSL" - and the connection will get upgraded to an encrypted connection. - NOTE: No username or password will be sent unencrypted!

1 Nov 2017 | 12:00 AM

Add reply