Fix email errors
Sending errors and sign-in problems in mail apps, what they mean, and how to fix them, from the email standards and each provider’s own settings.
Checking a domain or a message? Try the free email tools.
Sending errors
- SMTP error 550 5.7.1: what it means and how to fix it
550 5.7.1 is a permanent refusal: the receiving server will not take the message for a policy reason. The words after the code say which one, usually relaying denied, a sender or recipient rule, or a spam block.
- SMTP error 550 5.1.1: the recipient address does not exist
550 5.1.1 means the receiving server says the mailbox you wrote to does not exist (RFC 3463: "bad destination mailbox address"). It is permanent: check the spelling, or ask the person for their current address.
- SMTP error 554 5.7.1: message rejected
554 means the transaction failed (RFC 5321) and 5.7.1 means not authorized (RFC 3463): a permanent rejection for a policy reason. The text after the code names the server that refused the message and why.
- SMTP error 530 5.7.0: authentication required or STARTTLS first
530 5.7.0 means the outgoing server will not take your message yet: it wants you to sign in ("Authentication required", RFC 4954) or to switch on encryption first ("Must issue a STARTTLS command first", RFC 3207). Gmail uses this code for both.
- SMTP error 535: authentication failed when sending
535 means the outgoing server rejected the username or password your mail app sent; RFC 4954 defines 535 5.7.8 as "authentication credentials invalid". With Gmail, iCloud, Yahoo and AOL the usual fix is an app password instead of your normal password.
- SMTP error 552 5.2.2: the recipient’s mailbox is full
552 5.2.2 usually means the recipient’s mailbox is full (RFC 3463: mailbox over its quota), and only they can free up space. Microsoft 365 also uses 5.2.2 for "submission quota exceeded", which is about your own sending limit.
- SMTP error 421 4.7.0: try again later
421 4.7.0 is temporary: the server is closing the connection (RFC 5321) for a security or policy reason (RFC 3463). Your server should retry on its own; if it keeps happening, the text explains what to change.
- SMTP error 451 4.7.1: try again later (greylisting)
451 4.7.1 is a temporary deferral: the receiving server asks your server to try again later. It is often greylisting, where a server turns away the first attempt from a new sender and accepts the retry.
- SMTP error 550 5.7.26: Gmail blocked unauthenticated mail
550 5.7.26 is Gmail refusing a message it could not authenticate: neither SPF nor DKIM passed, or the From domain’s DMARC policy said to reject it. The fix is in your domain’s DNS records or the service you send through.
- Can’t send from a mail app? Port 25 may be blocked
Many networks block outgoing connections on port 25 to stop spam from infected computers. Port 25 is for servers relaying to each other; mail apps should send on port 587 with STARTTLS or 465 with SSL/TLS, with sign-in (RFC 6409, RFC 8314).
Signing in to a mail app
- Gmail keeps asking for your password in a mail app
Gmail no longer accepts your Google account password from mail apps. Sign in with Google if the app offers it, or turn on 2-Step Verification and use an app password. This also fixes "535 Username and Password not accepted".
- Gmail app passwords option is missing
Google shows app passwords only when 2-Step Verification is on. The option can still be missing if you use only security keys, have Advanced Protection, or use a work or school account whose admin turned it off. Then sign in with Google instead.
- iCloud Mail password not accepted in a mail app
Use an app-specific password, not your Apple Account password. Create one at account.apple.com under Sign-In and Security, then App-Specific Passwords. Your Apple Account needs two-factor authentication.
- Yahoo Mail not working in a mail app
Generate an app password on your Yahoo Account Security page and use it instead of your normal password, with your full Yahoo address as the username.
- AOL Mail not working in a mail app
If your mail app does not open AOL’s own sign-in page, use an app password from your AOL Account Security page, with your full @aol.com address as the username.
- Outlook.com or Hotmail password not accepted in a mail app
Microsoft stopped accepting basic password sign-in for Outlook.com, Hotmail and Live accounts on September 16, 2024. IMAP, POP and SMTP now need Microsoft’s own sign-in (Modern Auth, OAuth 2.0), so remove the account and add it again with the app’s Microsoft or Outlook.com option.
- How to turn on IMAP in Outlook.com
In Outlook.com, open Settings, Mail, Forwarding and IMAP, turn on "Let devices and apps use IMAP", and save.
- Microsoft 365 IMAP "authentication failed" for a work account
Exchange Online no longer accepts basic (password) authentication for IMAP, so the mail app must sign in with Microsoft’s Modern Auth (OAuth 2.0). If that still fails, your admin may have turned IMAP off for your mailbox or blocked it with security defaults or Conditional Access.
- Microsoft 365 can’t send from a mail app: SMTP AUTH is turned off
Exchange Online is refusing SMTP AUTH, the authenticated sending a mail app uses on smtp.office365.com. A Microsoft 365 admin must turn on Authenticated SMTP for your mailbox or the organization; security defaults can still block it.
- Fastmail IMAP not working in a mail app
Fastmail accepts only an app password in other mail apps. Create one in Fastmail’s settings under Privacy & Security with access to mail (IMAP and SMTP), and use your full Fastmail address as the username.
- Zoho Mail IMAP access not available
Turn on IMAP in Zoho Mail under Settings, Mail Accounts, your address, then IMAP Access. Zoho does not include IMAP in every plan, so check yours if the option is missing.
- GMX IMAP stopped working
Turn POP3 and IMAP access back on in GMX: open Email, Settings, POP3 & IMAP, tick the option to allow access via POP3 and IMAP, and save.
- Proton Mail in another mail app: IMAP through Bridge
Proton Mail is end-to-end encrypted, so other mail apps reach it through Proton Mail Bridge, which needs a paid plan. Install Bridge, sign in, and use the server details and password Bridge shows, not your Proton password.
- Mail server certificate name mismatch
The mail server’s certificate does not cover the server name your app is using, often mail.yourdomain.com on shared hosting. Use the incoming and outgoing server names your host lists for SSL/TLS instead.