Gmail Blocking Your Emails or Sending Them to Spam? Causes and Fixes
If Gmail is blocking your emails or your emails are going to spam, the cause is almost always one of three things: your domain isn't authenticated the way Gmail expects (SPF, DKIM, DMARC), your sending server's setup or reputation has a problem, or recipients are marking your mail as spam. The bounce message you get back usually tells you which one.
If instead you're the one not receiving mail in your own Gmail inbox, the fix is usually on your side: the Spam folder, an inbox tab, a filter, a forwarding or POP setting, or full storage. Both cases are covered below, so jump to the part that matches your situation.
Requirements, codes and thresholds here are based on Google's official help pages as of November 2026. Google updates these policies, so confirm the details on the linked pages before making changes.
First, figure out which side of the problem you're on
"Gmail isn't delivering my email" can mean two very different problems. Find your row and skip to the matching section.
| What you see | Your side | Where to look |
|---|---|---|
| An email you expect (a sign-up confirmation, a reply from a client) never shows up in your Gmail | Receiver | Spam, tabs, filters, blocked senders, forwarding and POP/IMAP, storage |
| You get a "Delivery Status Notification (Failure)" or a bounce with a 4.x.x or 5.x.x code | Sender | The error code, SPF/DKIM/DMARC, reverse DNS, TLS |
| No bounce, but Gmail users tell you your emails are going to spam | Sender | Authentication and alignment, spam rate, sending practices |
If you check everything on the receiving side and still find nothing, the problem is probably with the sender, and the second half of this article is what they need to read.
Not receiving email in your Gmail inbox: what to check
Google's own checklist for this is the help page Gmail messages are missing. The steps below follow it. Do them in Gmail on a computer, in a browser: it's easier to see your settings there, and it rules out problems with phone apps or other mail clients.
- Search Spam and Trash too. In the search bar, open Show search options, change the dropdown next to "Search" to Mail & Spam & Trash, and search for the sender's address or a word from the subject. Normal searches skip Spam and Trash, and messages there are permanently deleted after 30 days. If you find the email in Spam, open it and select Not spam.
- Check the other inbox tabs. With the Default inbox type, Gmail sorts mail into Primary, Social, Promotions, Updates and Forums. Receipts, newsletters and account notices often land in Promotions or Updates. Dragging a message onto the Primary tab moves it and helps Gmail learn where similar mail should go.
- Look for filters and blocked senders. Go to Settings (gear icon) > See all settings > Filters and Blocked Addresses. Any filter that says "Delete it" or "Skip Inbox" can make mail seem to vanish; edit or delete it. Mail from a blocked sender goes straight to Spam, so if the sender is listed there, select it and click Unblock selected addresses.
- Review forwarding and POP/IMAP. On the Forwarding and POP/IMAP tab, if you forward mail, choose Keep Gmail's copy in the Inbox. If you see a forwarding address you don't recognize, select Disable forwarding; unfamiliar forwarding can be a sign that someone else has access to your account, so also review Third-party apps & services in your Google Account and remove anything you don't recognize. If POP is set to delete or archive Gmail's copy, switch it to keep Gmail's copy in the inbox and save.
- Check your storage. Every Google Account gets up to 15 GB of free storage, shared between Gmail, Google Drive and Google Photos. When it fills up, your ability to send and receive email in Gmail can be impacted. Free up space by deleting large files or old emails with big attachments.
- Check other apps and devices. There is only one copy of each Gmail message, so deleting or archiving it in a synced app (Outlook, Apple Mail, a phone client) removes it from Gmail as well. Look for auto-delete or auto-archive rules in those apps.
Still missing? Rule out the sender's side
If none of that turns up the message, it probably never reached Gmail. Ask the sender a few questions:
- Did they get a bounce? A typo in your address returns
550 5.1.1, meaning the account doesn't exist. Have them check for misspellings, stray dots or spaces. - Is your mailbox full? Senders see
452 4.2.2when your inbox is out of storage. That's temporary. An account that is both full and inactive returns552 5.2.2, which is permanent. Free up space, then ask them to resend. - Is it just late? Codes starting with 4 are temporary deferrals. The sending server normally retries later, so the message can arrive with a delay rather than not at all.
- Is their domain authenticated? Gmail can send unauthenticated mail to spam or reject it outright. If the sender is a company or an online service, point them to the sender sections below.
On a Google Workspace (work or school) account, your administrator can use Email Log Search to trace messages, so start there.
Gmail blocking your emails: read the bounce code
When Gmail refuses a message, the sending server returns a bounce. If you sent from Gmail, it usually comes from "Mail Delivery Subsystem" with the subject "Delivery Status Notification (Failure)". Find the three-part code in it. 4.x.x means a temporary rejection; the sender's server will usually retry. 5.x.x means the message was refused permanently. A typical example:
550 5.7.26 This mail has been blocked because the sender is unauthenticated.
These are the codes you're most likely to see, taken from Google's Gmail SMTP errors and codes reference:
| Code | What Gmail is telling you | Check first |
|---|---|---|
| 550 5.7.26 | The sender is unauthenticated, or the message failed the sending domain's DMARC policy | SPF, DKIM and DMARC |
| 550 5.7.27 | The message didn't pass SPF | Is the sending server included in your SPF record? |
| 550 5.7.30 / 421 4.7.30 | The message didn't pass DKIM (blocked / rate limited) | DKIM signing and the published key |
| 421 4.7.32 | The From: header domain isn't aligned with the authenticated domain | DMARC alignment |
| 421 4.7.40 / 550 5.7.40 | The sending domain has no DMARC record | A TXT record at _dmarc |
| 550 5.7.25 | The sending IP has no PTR (reverse DNS) record | PTR and matching forward DNS |
| 421 4.7.29 / 550 5.7.29 | The message wasn't sent over TLS | TLS on the sending server |
| 421 4.7.28 | Gmail detected an unusual rate of email and is throttling you | Volume and sending speed |
| 550 5.7.1 | Likely unsolicited mail, or very low reputation of the sending IP | Content, list quality, reputation, blacklists |
| 550 5.7.28 | An unusual rate of unsolicited mail from your IP | Compromised accounts or bulk sends |
One more case if you send from a personal Gmail account: Gmail also limits sending to 500 emails a day or one email to more than 500 recipients. Going over it blocks sending for roughly 1 to 24 hours, and the limits differ by account type. It is a temporary block, not a reputation problem. For large mailings, Google suggests using a Google Group instead.
Gmail's sender requirements (in effect since February 2024)
Since February 2024, Google's Email sender guidelines apply to everyone who sends to personal Gmail accounts. All senders must:
- Set up SPF or DKIM for the sending domain
- Have valid forward and reverse DNS (PTR) for the sending IP, with the two matching
- Use TLS when transmitting email
- Keep the spam rate reported in Postmaster Tools below 0.3% (Google recommends staying under 0.1%)
- Format messages according to RFC 5322 and not impersonate Gmail From: headers
Bulk senders, meaning those sending roughly 5,000 or more messages a day to Gmail accounts, must also:
- Set up both SPF and DKIM
- Publish a DMARC record (a policy of
p=noneis acceptable) - Align the From: domain with the SPF or DKIM domain
- Support one-click unsubscribe for marketing and subscribed messages, with a visible unsubscribe link in the body
The 5,000 count is per primary domain, so mail from subdomains adds up. Once you meet the criteria, Google treats you as a bulk sender permanently. According to Google's sender guidelines FAQ, Gmail started ramping up enforcement on non-compliant traffic in November 2025, which means temporary and permanent rejections or delivery to spam. The guidelines don't apply to messages sent to Google Workspace accounts, only to personal Gmail. Yahoo publishes closely matching requirements.
A minimal DNS setup looks like this (documentation values only):
example.com. TXT "v=spf1 ip4:203.0.113.10 -all" selector1._domainkey.example.com. TXT "v=DKIM1; k=rsa; p=(public key)" _dmarc.example.com. TXT "v=DMARC1; p=none; rua=mailto:dmarc@example.com" mail.example.com. A 203.0.113.10 10.113.0.203.in-addr.arpa. PTR mail.example.com.
DKIM keys need to be at least 1024 bits for personal Gmail; Google recommends 2048. For a step-by-step walkthrough, see how to set up SPF, DKIM and DMARC.
Emails going to spam or rejected: a step-by-step fix
Whether you're getting hard bounces or your emails are quietly going to spam, work through these steps in order.
- Write down the exact bounce code. Match it against the table above to see whether you're dealing with authentication, TLS, volume or reputation. Don't guess; the code is the most specific clue you have.
- Send a test message and read the headers. Send to a Gmail address you control, open the message in a browser, then choose More > Show original. In the authentication results, look for
spf=pass,dkim=passanddmarc=pass, and check that the domain in From: matches the domain that passed. - List every system that sends as your domain. Your own mail server, a newsletter platform, a CRM, website contact forms, invoicing tools. A common cause of failures is one service that was never added to SPF or never set up to sign with DKIM.
- Check blacklists. Run your sending IP and domain through a blacklist (DNSBL) check. Gmail relies on its own reputation data, so a public listing isn't automatically the reason Gmail blocks you. But a listing often points to a compromised account, an open form being abused or a shared IP with bad neighbours, and it will hurt delivery to other providers. If you're listed, see what to do when email isn't delivered because of a blacklist.
- Set up Postmaster Tools. Add your domain to Postmaster Tools (the DKIM
d=domain or the SPF Return-Path domain) and verify it with the TXT or CNAME record it gives you. The dashboards show spam rate, authentication and delivery errors, and the Compliance status dashboard marks each sender requirement as Compliant or Needs work. Low-volume senders may see no data. Changes can take up to 7 days to show up. - Fix how you send, not just DNS. Only mail people who asked for it, confirm addresses at sign-up, process unsubscribes promptly, and consider dropping recipients who never open your mail. Google notes that the longer a high spam rate continues, the more likely future messages are to go to spam.
- Ramp back up gradually. After fixing a problem, don't resend your entire backlog at once. A sudden spike is exactly what triggers rate limits such as 421 4.7.28.
Be realistic about timing. Correct DNS takes effect quickly, but a damaged reputation recovers only as Gmail sees consistently clean mail from you, and nobody can promise that by a particular date.
We introduce providers who take on delisting requests, consulting and advice (from JPY 50,000). Delisting is decided by each list operator and cannot be promised.
Get helpThis site may receive a referral fee from listed providers. About
FAQ
Why are my emails going to spam in Gmail when there is no bounce?
Gmail accepted the message but its filters judged it suspicious. The usual reasons are missing or failing authentication, a From: domain that isn't aligned with SPF or DKIM, a high rate of recipients marking your mail as spam, or a poor sending reputation. Check the message headers with Show original, then look at Postmaster Tools for your spam rate.
Do the Gmail sender requirements apply if I send fewer than 5,000 emails a day?
Yes, partly. Every sender to personal Gmail needs SPF or DKIM, valid forward and reverse DNS, TLS, and a spam rate under 0.3%. The extra rules (both SPF and DKIM, DMARC, alignment, one-click unsubscribe) are mandatory for bulk senders, but setting them up at any volume is sensible.
If I get removed from a blacklist, will Gmail stop blocking my emails?
Not necessarily. Gmail makes its own reputation decisions. Removing the cause of the listing helps, but you should also make sure authentication passes and watch your spam rate in Postmaster Tools while things improve. No one can guarantee delivery.
Emails didn't arrive while my Gmail storage was full. Will they come through later?
Maybe. A full mailbox causes a temporary 452 4.2.2 error, and the sending server retries for a while. How long it keeps trying depends on the sender's server, so after freeing space, ask anyone whose email you were expecting to send it again.
Do these requirements apply to Google Workspace recipients?
No. Google's sender guidelines cover mail sent to personal Gmail accounts, not to Google Workspace accounts. They do apply to mail sent from a Workspace account to personal Gmail. Unauthenticated mail can still be filtered as spam in Workspace, so authentication matters either way.
Official pages used
The facts in this article were checked against the official pages below at the time of publication. Policies and behavior change without notice, so check the official pages before relying on anything important.
- Email sender guidelines (Google Workspace Admin Help)
- Email sender guidelines FAQ (Google Workspace Admin Help)
- Gmail SMTP errors and codes
- Gmail messages are missing (Gmail Help)
- Postmaster Tools dashboards (Gmail Help)
- Set up Postmaster Tools (Gmail Help)
- Emails that bounce or are rejected (Gmail Help)
- Inbox categories and tabs (Gmail Help)
- Block or unblock a sender (Gmail Help)
- Google Account storage (Google One Help)
- Trace an email with its full header (Gmail Help)
- Sender Best Practices (Yahoo Sender Hub)
Related guides
SPF, DKIM and DMARC setup with copy-ready DNS records, the 10-lookup limit, 2048-bit keys, a safe p=none rollout, and Gmail, Yahoo and Outlook rules.
Email blocked by a blacklist? Read the bounce code, check the causes in the right order, see which listings matter, and request removal the right way.