Recent Changes to SMTP Auth and SMTP Settings

Modified on Tue, 24 Mar at 3:47 AM

TABLE OF CONTENTS


Overview

Microsoft and Google have made significant changes to their authentication methods for SMTP services (March 2025). These changes impact how SEQTA connects to smtp.office365.com and smtp.gmail.com for sending emails.


Microsoft: Basic Authentication Deprecation

Microsoft will be retiring SMTP Auth for Office 365 SMTP as part of its efforts to enhance security. SMTP Auth, which involves sending usernames and passwords with every request, is being replaced by more secure methods.


Key Changes:

  • Deprecation Date: SMTP Auth will be deprecated by September 2025.
  • SMTP Server: The SMTP server remains smtp.office365.com.
  • Ports: Use port 587 with STARTTLS or port 25 with TLS.


Configuration Steps:

  1. Create App Passwords: Since SEQTA does not support modern authentication, you will need to create an app password for the authenticating account used by SEQTA. This can be done in the Office 365 admin center.
  2. Recommended Setup: Option 3 setup is recommended for setting up Office 365 SMTP. (Please see detailed instructions below by Microsoft)
    How to set up a multifunction device or application to send email using Microsoft 365 or Office 365
  3. High Volume Email (HVE) Service: Create High Volume Email (HVE) service accounts for enhanced security and management. HVE accounts can be used by SEQTA to deliver emails. (Please see detailed instructions below by Microsoft)
    Manage high volume emails for Microsoft 365 in Exchange Online Public preview
  4. Contact SEQTA Support: After implementing the necessary changes on your end, please contact SEQTA Support to configure these changes on the SEQTA server.


Google: SMTP Relay Changes

Google has also updated its SMTP relay service to enhance security. The smtp.gmail.com server now requires more secure authentication methods.


Key Changes:

  • SMTP Server: The SMTP server remains smtp.gmail.com.
  • Ports: Use port 587 with STARTTLS or port 465 with SSL/TLS.


Configuration Steps:

  1. App Passwords: Since SEQTA does not support OAuth, setting up app passwords for the authenticating account in SEQTA is the alternative. (Please see below instructions below by Google)
    Sign in with app passwords - Google Account Help
  2. Contact SEQTA Support: After implementing the necessary changes on your end, please contact SEQTA Support to configure these changes on the SEQTA server.

 

Please see below for official announcements by Microsoft and Google


For further assistance, please contact SEQTA support.

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article