ShareFile
View PDF

Custom SMTP Changes FAQ

January 20, 2026
Contributed by: 
P

Microsoft will deprecate basic authentication for custom SMTP on March 1, 2026. This feature allows notifications from ShareFile to have its sender appear as if the email came from their company (or a trusted proxy) rather than from ShareFile. The proposed change requires an OAuth-based relay solution to maintain functionality for customers using custom SMTP in ShareFile.

For more information, refer to Exchange Online to retire Basic auth for Client Submission (SMTP AUTH).

  • Who is affected by this change?
    • Organizations using Microsoft/Exchange-based email setups with the Custom SMTP feature in ShareFile are affected. If your organization does not use Exchange, you are not impacted.
  • What happens if no action is taken?
    • Email notifications sent through ShareFile using Custom SMTP may start failing on March 1, 2026, and will stop working entirely after April 30, 2026.
  • What is being done to address this?
    • Our engineering team is developing a new OAuth-based solution for Exchange users. We will share more details as soon as it becomes available.
  • What should we do now?
    • Review your current email configuration settings and determine if Custom SMTP is still required for your organization.

    If Custom SMTP is still required:

    • Consider switching to a different email provider, as non-Exchange providers are not affected by this change.
    • Enable the “Fallback to ShareFile” setting to avoid email delivery issues during the transition.
    • Identify an IT administrator to prepare for updates and monitor communications for new SMTP support.
  • How can I enable the “Fallback to ShareFile” setting?
    • To enable this setting, a ShareFile administrator should:
      1. Navigate to Account Settings from the left navigation.
      2. Select Advanced Preferences.
      3. Go to Email Settings.
      4. Under the SMTP Server section, click Configure SMTP Settings.
      5. Find the Fallback to ShareFile option and select “Yes” or confirm that it is already enabled.
  • When will the new solution be available?
    • We are actively working on the OAuth-based solution and will provide updates as soon as it’s ready.
  • Who can we contact for help?

For Non-Impacted Clients (Non-Exchange Accounts)

  • Are we affected by this change?
    • No. If your organization does not use Microsoft/Exchange-based email setups, you are not impacted by this change.
  • Do we need to take any action?
    • No immediate action is required. Your current email configuration will continue to work as expected.
  • Why are we receiving this communication?
    • We are sharing this information for awareness, as it may be relevant if your organization uses our Custom SMTP feature or plans to make changes in the future.
  • Should we still review our settings?
    • Yes, it’s always a good practice to review your email configuration periodically to ensure everything is working as expected.
  • Who can we contact if we have questions?
Custom SMTP Changes FAQ
January 20, 2026
Contributed by: 
P
January 20, 2026
Contributed by: 
P

In this article

Site feedback | Privacy and legal terms | Cookie preferences

About Us | Awards | Press Releases | Media Coverage | Careers | Offices | Security Center | License Agreement | Do Not Sell or Share My Personal Information

Copyright © Progress Software Corporation and/or its subsidiaries or affiliates. All Rights Reserved.

Progress and certain product names used herein are trademarks or registered trademarks of Progress Software Corporation and/or one of its subsidiaries or affiliates in the U.S. and/or other countries. See Trademarks for appropriate markings. All rights in any other trademarks contained herein are reserved by their respective owners and their inclusion does not imply an endorsement, affiliation, or sponsorship as between Progress and the respective owners.