Your email provider does not support OAuth2 – Mailbird

This provider does not support OAuth2

Not every email server supports OAuth2 sign-in. If Mailbird shows an error saying the host or provider does not support OAuth2, it usually means the server expects a traditional username-and-password connection instead.

This does not necessarily mean your account cannot be added. It usually means you need to choose a different setup method.

What this error usually means

You selected an account type that expects OAuth2, but the provider only supports password-based login.
You are connecting to a custom domain, business mail server, or on-premise mail server that does not offer OAuth2.
You selected the wrong provider during setup.

What to do next

Go back and review the account type you selected
If you chose Gmail, Outlook, Microsoft 365, or another OAuth2 provider by mistake, restart setup and select the correct provider or manual configuration option.
Use manual setup with IMAP/POP and SMTP
If your provider does not support OAuth2, add the account with your incoming and outgoing server settings instead.
Use an app password if your provider requires one
Some providers still use password-based setup, but require an app-specific password instead of your normal sign-in password when two-factor authentication is enabled.
Check your provider documentation
Confirm whether the provider supports OAuth2 for third-party email clients. Some providers support it only for certain account types.

When app passwords matter

If your provider supports standard IMAP/SMTP but blocks your normal password because of two-factor authentication, generate an app password and use that in Mailbird. This is common with some Microsoft, Yahoo, Apple, and business-hosted accounts.

Helpful companion articles

Still not sure which setup to use?

If you do not know whether your provider supports OAuth2, contact your email provider or IT administrator and ask whether third-party clients should connect using OAuth2, Exchange, IMAP, or POP3.