Will Microsoft Ending Online Basic Authentication and Exchange Affect Elliott SMTP Emails?

Will Microsoft Ending Online Basic Authentication and Exchange Affect Elliott SMTP Emails?

Release Date: 9/29/22
Version: 8.5 & Up

Q - Microsoft announced they will end basic authentication for Azure / 365 and Exchange online by October 1st, 2022.  Does that mean Elliott SMTP email support will no longer work with Microsoft Exchange online, and in Outlook 365 or Office 365 after this day?

A - The short answer is that Elliott SMTP email sending will continue to work with Exchange online. 

According to the announcement, Microsoft Exchange online will stop supporting most of the basic authentication by Oct 1st, 2022, except SMTP AUTH. Elliott uses SMTP AUTH to communicate when sending emails and will continue to work. 

According to Microsoft's explanations, SMTP AUTH will still be available when Basic authentication is permanently disabled on October 1, 2022. The reason why SMTP will still be available is that many multi-function devices (such as printers and scanners) can't be updated to use modern authentication. See the following link for more information:

It is possible SMTP authentication method is disabled.  You can either enable that with PowerShell or go to Exchange on-line admin to enable the mail box to use "Authenticated SMTP". See the following YouTube Video for details:

You should make sure your Elliott version is updated to V8.5b.914 or after to make sure TLS 1.2 is supported. Otherwise, you may receive the following error message:

    ERROR: A call to SSPI failed



Also, in Exchange online, SMTP AUTH support should still be enabled.  Otherwise, you may receive the following error message in Elliott:
The SMTP server requires a secure connection or the client was not authenticated. The server response was: 5.7.57 Client not authenticated to send mail. Error: 535 5.7.139 Authentication unsuccessful, basic authentication is disabled:
or
The SMTP server requires a secure connection or the client was not authenticated. The server response was: 5.7.57 Client not authenticated to send mail. Error: 535 5.7.139 Authentication unsuccessful, SmtpClientAuthentication is disabled for the Tenant. Visit https://aka.ms/smtp_auth_disabled for more information.





EMK


    • Related Articles

    • Configuring Elliott V8.0

      Configuring Elliott V8.0 After installing Elliott V8.0, you need to make some configuration changes. If this is the first time you have started Elliott, the system will detect that the EL800.CFG file does not exist in your startup <root>\Bin ...
    • Creating HTML Emails for Professional Presentation

      Release Date: 12/23/2020 Version: 8.5 and Higher Background By default, Elliott's email is in text format. Elliott "EM" API calls will allow developers to create an email document to send out. For more information on "EM" API, please refer to the ...
    • Elliott SMTP Email Settings for Outlook 365 or Hosted Email Solutions

      Release Date: 1/19/2018 Revision Date: 9/26/2022 Version: 8.0 & Up Introduction Starting with Elliott V8, we support both SMTP and MAPI interfaces for sending emails. MAPI is the old email interface method, which we find more and more difficult to ...
    • How Do I Configure Elliott V8 Email (SMTP) Settings?

      Q - I'm trying to instruct Elliott 8 to send the shipment emails using SMTP instead of Outlook (MAPI,) and I'm not sure where to put the SMTP info. A - You will use EL800CF.EXE in the <ElliottRoot>\Bin folder to configure the SMTP settings. Where ...
    • Setting up a Google Gmail Account in Elliott SMTP Configuration

      Release Date: 10/19/2017 Revised Date: 08/01/2024 Revised on 07/31/2024: Starting on September 30, 2024, less secure apps, third-party apps, or devices that have you sign in with only your username and password will no longer be supported for Google ...