Follow updates from this page

Follow updates from this page

E-mail : *

SL eBanking Customers

TLS 1.2 encryption required by Office 365 after 10/31/2018

Effective October 31, 2018 the use of Microsoft Office as an email relay server will require TLS 1.2 encryption.

See this link for more details from Microsoft:

Why is this important to you?

It’s important ONLY if:

  • You use SK Global (formerly Sandler-Kahne Software) eBanking Suite for Dynamics SL
  • You are using APEFT, AREFT or the Wire Transfer Plus module
  • And you send vendor/customer remittance emails using Office 365 as your mail relay server (per below from eBanking Setup)

Our updated release v11 now supports TLS 1.2 (any prior release does not).

If you do not normally do your own SL eBanking upgrades, please contact your reseller prior to upgrading eBanking to v11, so they may assess its overall impact in your environment. Upon determining to proceed with eBanking v11, you will need to download and install this release to continue the use of as your email relay server.

Here are the download links for v11 of the eBanking Suite for Dynamics SL:





SL versions prior to 2011
These eBanking versions are out of “update” support (phone support still available).  Therefore using as an email relay server with these older versions after October 31, 2018 will no longer be possible.

Once v11 is installed, the setting is very obvious.  In eBanking Setup set the SSL/TLS mode to TLS 1.2.  Then use the Test Email button to verify emails are working correctly.

If the email test fails, it’s possible that TLS 1.2 is not enabled on the machine where DD95000.exe is running (emails are sent from the machine that’s running eBanking setup and Create and Send files, not the SQL server machine).

Here is a link to a tool that can be used to review and modify SSL/TLS settings on Windows machines:

An upgrade to v11 from a SL eBanking version prior to v10.9 requires a new unlocking key.  Contact

For technical questions, please contact