Overview
Some email providers and mail servers do not support OAuth2. If Mailbird Next tells you that the host does not support OAuth2, it usually means you selected the wrong provider type or chose a sign-in method your provider does not offer.
What this means
OAuth2 is a modern browser-based sign-in method used by providers such as Google and Microsoft. Many other providers still rely on standard password-based setup or app-specific passwords instead.
How to fix it
Check that you selected the correct account type. For example, personal Outlook accounts should be added through the Outlook flow, while other providers may need manual IMAP, POP3, or SMTP setup.
Switch to manual setup if your provider does not offer OAuth2. Enter the incoming and outgoing server details exactly as provided by your email service.
Use an app password if your provider requires one. Some services require a separate app-specific password when two-factor authentication is enabled.
Review your provider's authentication requirements. Some business mail systems support only certain sign-in methods depending on admin settings.
Examples
Gmail: Normally supports OAuth2 and should usually be added with the Gmail option.
Microsoft personal accounts: Should normally be added with the Outlook option.
Custom domains and private mail servers: Often require manual IMAP/SMTP setup instead of OAuth2.
Still need help?
If you are unsure which option to choose, contact your email provider or your IT administrator and ask which protocol and authentication method your account supports.