Skip to content
NagentNagent
Log inSign upHire your AI Growth Team
NagentNagent
Log inSign up

Why is Gmail rejecting my emails with a 550 error?

8 Minutes read
Published:
A 550 from Gmail is a permanent rejection, and the code after it says why: a mailbox that does not exist, failed SPF, DKIM or DMARC, a sender reputation problem, a sending limit or a malformed message. Find the full code, then fix that one cause.
PB
Pratap BeheraNov 14, 2026·8 min read
Why is Gmail rejecting my emails with a 550 error?

A 550 from Gmail means its server permanently refused your message, and the enhanced code that follows tells you why. The most common causes are an address that does not exist (5.1.1), mail that failed SPF, DKIM or DMARC (5.7.26, 5.7.27, 5.7.30, 5.7.40), a reputation or "likely unsolicited" block (5.7.1, 5.7.28), a sending limit on your own account (5.4.5) or a malformed message. Find the full code in the bounce, fix that one cause, and do not simply resend.

Every code below is from Google's own SMTP error reference, read on 24 October 2026. We make Nagent, whose outbound research lead is NORA; how NORA's sends deal with bounces is in its own section near the end.

What does a 550 error from Gmail mean?

SMTP replies starting with 5 are permanent failures and replies starting with 4 are temporary (RFC 5321). After the three-digit reply, Gmail adds an enhanced status code in the form class.subject.detail, such as 5.7.26 (RFC 3463), plus a sentence of explanation.

So "550" alone tells you only that the message will not be delivered as sent. The enhanced code is the diagnosis:

  • 5.1.x: something wrong with the recipient address.

  • 5.2.x: something wrong with the recipient's mailbox.

  • 5.4.x: a routing or limit problem, often on your own side.

  • 5.5.x: a protocol problem, such as too many recipients.

  • 5.7.x: security or policy: authentication, reputation, formatting rules.

How do you find the full error code?

  • In a bounce message: open the "Delivery Status Notification" or "Undeliverable" email and look for the line starting 550 followed by a code like 5.7.26.

  • In your sending platform: open the bounced message's event log. Most platforms store the raw SMTP response.

  • In Google Workspace: the admin console's email log search shows the response for messages sent from your domain.

Copy the whole line. The sentence after the code often names the failing domain or IP.

What do the common Gmail 550 codes mean, and what causes each?

From Google's reference, grouped by cause:

  • 5.1.1: the account does not exist. Cause: a mistyped, invented or deleted address.

  • 5.2.1: the account is inactive, or is receiving mail at a rate that blocks more. Cause: a dormant mailbox.

  • 5.4.5: daily user sending limit or daily SMTP relay limit exceeded. Cause: your own Google Workspace user hit its quota. Google's sending limits are 2,000 messages a day for a standard user and 500 on trial accounts, and a user who hits a limit cannot send for up to 24 hours.

  • 5.5.3: too many recipients for this sender.

  • 5.7.0: sending or relay denied, including an account suspended for abuse.

  • 5.7.1: several messages. A policy at the recipient's domain blocks the mail; the message is likely unsolicited; the sending IP or domain has very low reputation; or the message breaks RFC 5322 (missing or multiple From headers, missing Message-ID, duplicate headers).

  • 5.7.24: the sending domain's SPF record has suspicious entries.

  • 5.7.25: the sending IP has no PTR record, or it does not match forward DNS.

  • 5.7.26: "This email has been blocked because the sender is unauthenticated." Also used when SPF hard-fails or the domain's DMARC policy rejects the message.

  • 5.7.27: the message did not pass SPF.

  • 5.7.28: an unusual rate of unsolicited email from your IP.

  • 5.7.29: the message was not sent over TLS.

  • 5.7.30: the message did not pass DKIM.

  • 5.7.40: the sending domain has no DMARC record.

How do you fix authentication failures (5.7.26, 5.7.27, 5.7.30, 5.7.40)?

  1. Find the sending service. Which tool sent the bounced email? CRM, outbound tool, marketing platform, your mailbox?

  2. Check SPF. Is that service included in your domain's SPF record? Is the record a single TXT record within the 10-lookup limit? Google's guide: set up SPF.

  3. Check DKIM. Is the service signing with your domain, and is its public key published? Google's guide: set up DKIM.

  4. Check DMARC. Does _dmarc.yourdomain exist? If it is set to reject, mail from any unlisted service fails. Google's guide: set up DMARC.

  5. Check alignment. The domain in the From header must match the SPF or DKIM domain. A tool sending "from" your domain but signing with its own fails here.

  6. Send a test to a Gmail account and read the original message headers: SPF, DKIM and DMARC should all show pass.

The classic cause of a sudden 5.7.26 is a new tool added to the stack, or a DMARC policy tightened, without the new sender being authorised first.

How do you fix "likely unsolicited" and reputation blocks (5.7.1, 5.7.28)?

These are about how recipients have reacted to your mail, so DNS changes alone will not clear them.

  1. Stop the campaign that triggered them.

  2. Check complaints. Google's sender guidelines ask senders to stay below 0.10% spam rate and never reach 0.30%, as Unify also notes (Unify). Look at Postmaster Tools.

  3. Check suppression. Are opt-outs and earlier complaints being re-mailed by another tool?

  4. Narrow targeting to the strongest-fit accounts and contacts.

  5. Cut volume and raise it slowly after clean weeks.

  6. Separate cold outbound onto its own sending domain so customer mail is not dragged down with it.

What if you see 5.1.1 on many addresses?

That is a list problem. Hard bounces tell mailbox providers you do not know who you are writing to.

  • Verify addresses before every campaign, not only when the list was built.

  • Suppress every hard-bounced address permanently.

  • Watch the rate. Apollo treats a bounce rate consistently above 2% as a list-hygiene problem (Apollo).

  • Be careful with catch-all domains, which accept any address at first and bounce later.

What is the difference between a 550 and a 421 from Gmail?

A 421 is temporary. Gmail uses 4.7.x codes to rate-limit mail that fails SPF (4.7.27), DKIM (4.7.30), alignment (4.7.32) or has no DMARC record (4.7.40), and 4.7.28 when it sees an unusual rate of unsolicited mail. Your sending server retries a 421. If the cause is not fixed, the same problems tend to turn into 550s. Treat a run of 421s as an early warning.

Why did Gmail start rejecting mail that used to go through?

  • Enforcement tightened. Apollo notes that Gmail began rejecting non-compliant bulk mail from November 2025 (Apollo).

  • A new sender joined the stack without SPF or DKIM.

  • A DKIM key was rotated and the new public key was not published.

  • Volume jumped from a new campaign or a new AI tool.

  • A list was imported without verification.

What should you check first when the code is unclear?

If the bounce text is truncated or your platform hides it, work through this order. Each step rules out a cause cheaply before you reach the expensive ones:

  1. One recipient or many? One address failing points to that address. Many addresses at many domains point to you.

  2. One tool or all? If only mail from your outbound tool bounces, look at that tool's SPF and DKIM first.

  3. Did anything change this week? A new tool, a DNS edit, a DMARC policy change, a new list or a volume increase.

  4. Do test emails to your own Gmail account pass SPF, DKIM and DMARC?

  5. What does Postmaster Tools show for spam rate and compliance status?

Step 3 is often the quickest to answer, so ask it early.

Where Nagent fits

We make Nagent. "Nagent is multiplayer AI for growth: people and AI agents in one shared context, delivering the number." NORA is the AI Outbound Research Lead on SERA's Sales team.

  • Domain status in plain words. NORA's email goes out through your own sending account. The Integrations page reports the domain as Verified, Pending, Failed, Partially verified or Not found, and Check domain re-reads it at any time. Both SPF and DKIM records are required before sending is allowed.

  • Hard bounces suppress. A permanent bounce writes the address to the workspace suppression list as Hard-bounced; a temporary bounce writes nothing. Every send is checked against the list as it leaves, so a bounced address is not mailed again.

  • Fewer bad addresses. Contacts are revealed only for companies scoring 70 or more out of 100 against your profile, and on a new workspace every send waits for a person.

What it does not do: Nagent does not diagnose SMTP codes for mail your other tools send, or manage your DNS records. Work is metered in credits; see pricing.

Frequently Asked Questions

Should I resend an email that got a 550?

Not unchanged. A 550 is permanent for that message as sent. Fix the cause the code names, then send again only if the address is valid.

How do I fix 550 5.7.26 in Gmail?

Make sure the sending service is authorised in SPF, signs with DKIM on your domain, and that the From domain aligns with one of them. If your DMARC policy is reject, add the service before sending.

Does a 550 error hurt my domain reputation?

Occasional bounces are normal. Repeated hard bounces and "unsolicited" blocks signal poor list quality and targeting, so fix the cause quickly.

Why are my cold emails bouncing?

Usually unverified or stale addresses (5.1.1), missing authentication on a new sending tool (5.7.26) or volume and complaints that trip reputation blocks (5.7.1, 5.7.28). Read the code first.

See how NORA suppresses hard bounces and opt-outs at send time: book a demo.

Continue learning

Related agents

Agents that match this read.

Browse all 200+ agents
Select Category
Sales

What spam complaint rate is too high for Gmail?

Google asks senders to keep the spam rate in Postmaster Tools below 0.10% and never reach 0.30%. At 0.3% or above, bulk senders lose access to mitigation until they stay under it for seven days. What the numbers mean and how to bring them down.

Sales

How to meet the Gmail and Yahoo bulk sender requirements

Authenticate with SPF, DKIM and DMARC, align your From domain, add one-click unsubscribe headers, honour opt-outs within two days and keep spam complaints below 0.3%. A step-by-step checklist with the exact rules and how to check each one.

Sales

AI SDR emails get low reply rates and hurt our domain. What is the alternative?

Low replies and a damaged domain usually come from the same cause: high volume of thinly researched email. The alternative is research-first outreach, fewer sends, a person approving each one, and a protected sending domain. Here is how to diagnose it and recover.

Sales

AI SDR agents that work with HubSpot and Gmail without hurting domain reputation

An AI SDR protects your domain when it sends from authenticated mailboxes you control, stays far below Gmail's limits, writes every reply and opt-out back to HubSpot and waits for a person on first touches. Here is the setup and how the main options handle it.

Sales

AI outbound tool that drafts personalised emails but waits for my approval before sending

Several AI outbound tools draft personalised emails and hold them for a person: Unify queues drafts for approval, Artisan offers approve-before-send, and Nagent's NORA holds every send on a new workspace. Here is how they differ and what real approval should mean.

Sales

Can Jasper or Copy.ai actually run outbound sales, or do they just write emails?

Jasper writes; Copy.ai researches and writes. Neither describes sending, sequencing, reply handling or suppression on its own site, so neither runs outbound end to end. Here is what each covers and what you still need.