Theme
Sending email when your provider no longer accepts an SMTP password
Syncplify Server! sends mail for you: notifications to SuperAdmins and Admins, the invitations users send when they share a file, and the messages your event handler scripts send with SendMail(). For years that meant an SMTP server, a user name and a password.
Microsoft and Google are both ending that way of signing in:
- Microsoft 365 turns user name and password sign in for SMTP off by default for existing tenants at the end of December 2026. An administrator can turn it back on for a while; Microsoft will announce the date it goes away for good in the second half of 2027.
- Google Workspace stopped accepting an account password over SMTP in March 2025. What still works is an app password, which needs 2 Step Verification on the sending account.
If mail from your server stopped, or your mail administrator told you it is about to, this page is for you.
The fix: Syncplify Server! 8.14.0
From version 8.14.0 the mail settings have a Delivery method. Next to SMTP server there are two new ones, Microsoft 365 and Google Workspace. They do not use SMTP and they do not use a password. The server hands each message to the provider over HTTPS, signed in as an application you register with the provider once:
- For Microsoft 365, an app registration in Microsoft Entra with one permission,
Mail.Send. - For Google Workspace, a service account in Google Cloud, delegated one scope,
gmail.send.
Both can send mail and nothing else: neither can read or delete a single message. Nobody has to sign in by hand, now or later, so there is no token that expires because a person was away.
Nothing changes for a server that keeps its SMTP settings. After the update it sends exactly the way it did.
Setting it up
There are two places with mail settings, and each has its own delivery method:
- SuperAdmin UI, Global Configuration, Email: the notifications to SuperAdmins and Admins.
- Admin UI, System, SMTP, once per virtual site: share invitations and
SendMail().
The manual walks through both providers step by step, with every screen you need on the provider's side: Email through Microsoft 365 and Google Workspace. In short:
Microsoft 365
- In the Microsoft Entra admin center, register an application and copy its Application (client) ID and Directory (tenant) ID.
- Give it the Application permission
Mail.Sendof Microsoft Graph, and grant admin consent. - Create a client secret and copy its Value (not the Secret ID).
- In Syncplify Server!, choose the delivery method Microsoft 365, enter the sender address, the two IDs and the secret, save, and send a test email.
Google Workspace
- In the Google Cloud console, enable the Gmail API, create a service account, and download a JSON key for it.
- In Syncplify Server!, choose the delivery method Google Workspace, enter the sender address, choose the key file, and save. The page then shows a Client ID for delegation.
- In the Google Admin console, as a super administrator, open Security, Access and data control, API controls, Manage Domain Wide Delegation, and authorize that Client ID for the scope
https://www.googleapis.com/auth/gmail.send. - Send a test email.
TIP
The test action tells you what is wrong and repeats the provider's own words. "The credentials are valid, but they are not allowed to send as this mailbox" right after step 3 of the Google setup usually means the delegation has not reached Google's servers yet: Google allows itself up to 24 hours, though minutes are the norm.
Things worth knowing before you start
- A Microsoft client secret expires, after two years at most. Note the date. When it passes, mail stops and the test says the provider refused the credentials. Create a new secret before then and replace it in the settings.
- Use a mailbox made for the purpose. A shared mailbox in Microsoft 365 needs no license. In Google Workspace the sender must be a real user with Gmail turned on.
- The server needs outbound HTTPS (port 443) to
login.microsoftonline.comandgraph.microsoft.com, or tooauth2.googleapis.comandgmail.googleapis.com. Outbound SMTP is no longer needed for these two methods. - Scripts do not change.
SendMail()keeps its parameters and sends through whatever the virtual site is set to. Two things to check in a script that sends through a provider: the sender it passes must be the mailbox the site sends from, or an address that mailbox may send as; and with Microsoft 365 a message can carry only a few megabytes of attachments.
If you cannot update yet
On a version before 8.14.0 the server can only speak SMTP with a password, or with no sign in at all. Until you update:
- Google Workspace: create an app password for the sending account (it needs 2 Step Verification), and use it as the SMTP password with
smtp.gmail.com, port 587, TLS mode Explicit (STARTTLS). - Microsoft 365: ask your Microsoft 365 administrator to keep user name and password sign in for SMTP enabled for the sending mailbox. Microsoft allows this until the final removal date.
- Any provider: an SMTP relay inside your own network that accepts mail from the server's address without a password, and forwards it, keeps working with every version. Leave the user name and the password empty in the SMTP settings.
These keep mail flowing. They do not replace the update: the password based sign in they depend on is the very thing being retired.
More
- The manual: Email through Microsoft 365 and Google Workspace, the SMTP page of the Admin UI, and what changed in 8.14.0.
- If the test email keeps failing, contact our support with the exact message the test shows. It names the kind of failure and carries the provider's own explanation, which is usually all we need.