Why is a Gmail address not sending to another Gmail address?
Published 14 May 2025
Updated 6 Oct 2026
13 min read
Summarize with
Updated on 6 Oct 2026: We added Gmail sync checks and clarified sending limits, custom-domain routing, and upcoming send-as changes.
A message missing from the recipient's Inbox does not prove Gmail failed to send it. Gmail usually saves a sent message in Sent, delivers it elsewhere in the mailbox, delays it, or returns a bounce. When there is no inbox copy, no spam copy, and no bounce, first confirm that both addresses are personal Gmail accounts and that the message left Drafts, Scheduled, or Outbox. A Sent copy records the sending action, but does not prove delivery to the recipient's Inbox.
The answer changes when either address is a custom domain using Google Workspace, a group, a Gmail API integration, or a send-as identity. Those paths still look like Gmail to a user, but add routing or application controls. DNS authentication checks apply to a custom From domain; personal Gmail aliases do not require their owners to edit Google's DNS.
- Confirm whether both addresses are plain personal Gmail mailboxes, even if both users open their mail in Gmail.
- Review filters, blocks, forwarding, labels, group settings, and Workspace quarantine that can hide the message.
- Determine whether the sender used normal Gmail compose, Gmail API, send-as, delegation, or an app connection.
Confirm the Gmail account and sending path
Start with the simplest split: personal Gmail and custom domains opened in Gmail need different troubleshooting. Personal @gmail.com mail has Google-managed SPF, DKIM, and DMARC. A custom From domain has its own DNS and sending configuration; Workspace administrators also have routing controls and Email Log Search.
|
|
|
|---|---|---|
@gmail.com to @gmail.com | Google handles normal Gmail sending | Sent, then in:anywhere search |
Custom domain | Workspace, forwarding, or another provider | MX and headers |
Gmail API | Programmatic send | API response and Sent copy |
Two recipients fail | Pattern near sender side | Sender account or path |
Two senders fail | Pattern near recipient side | Recipient mailbox or domain |
Quick triage for a Gmail-to-Gmail delivery complaint.
Do not skip the basic evidence
A missing bounce does not prove delivery. A delivery error can arrive later, so check again after a few hours. Record the exact send time and recipient search results; Workspace administrators can add log evidence.
- Confirm the message is in web Gmail's Sent folder, rather than Drafts, Scheduled, or Outbox.
- Retest with a subject that has never been used before.
- Use an in:anywhere search to include archived mail, Spam, and Trash. All Mail alone excludes Spam and Trash.
- Check Inbox and Spam for a Delivery Status Notification from Mail Delivery Subsystem.
How to isolate the failure
The cleanest troubleshooting path is to reduce the test until there is only one variable left. Use a plain text message with a unique subject line, no signature, no links, and no attachments. If that arrives, add each removed item back separately. The first item that breaks delivery is your clue.
- Ask for the sender's Sent copy, timestamp with time zone, recipient address, subject, and any visible warning. Expand the recipient details to catch a wrong autocomplete suggestion or typo.
- Ask the recipient to search with in:anywhere and the unique subject. Confirm the search is in the intended Google Account.
- Look up MX records to identify incoming routing for any custom domain involved. Use received headers or SMTP settings to identify the outbound sending service.
- Separate normal Gmail compose from Gmail API, mobile app, send-as, forwarding, and delegated mailbox flows.
- Test one sender to two recipients and two senders to one recipient to narrow down which side to inspect.
Gmail delivery troubleshooting steps covering Sent mail, recipient search, and routing checks.
To identify who receives mail for a custom recipient domain, check that recipient domain's MX records. A sender domain's MX identifies incoming routing, not the service that sent a message. Forwarding and mail gateways also affect the route, so confirm the outbound path with received headers or the configured SMTP service.
MX and DMARC lookup commandsbash
dig MX example.org +short dig TXT _dmarc.example.org +short
Check Gmail sync and service status
Open the intended recipient account in web Gmail before assuming delivery failed. If the message is there but absent on a phone or desktop client, investigate that client's connection or sync. A missing notification alone does not mean a message is missing.
- Confirm the app is showing the same Google Account as web Gmail, then refresh the inbox.
- Check internet access and update the Gmail app. On Android, open Gmail > Settings > your account and enable "Sync Gmail"; also check device account sync and available device storage.
- If a connected mail client stopped updating after a password change, reconnect it using Google sign-in.
- If web Gmail fails too, test another browser with extensions disabled. If several accounts fail at the same time, check for a Gmail incident before changing mailbox or DNS settings.
Google's sync troubleshooting covers app refresh and Android sync settings. Check the Google Workspace Status Dashboard for reported Gmail disruptions. A clear status dashboard does not rule out an account-specific problem.
Recipient-side causes that look like non-delivery
If the sender has a Sent copy and no bounce, look closely at the recipient mailbox. Gmail has many places a message can land without being visible in the primary inbox, including Promotions or Updates tabs. Conversation view can bury a new reply inside an old thread. Filters can archive, label, forward, or delete. A blocked sender goes to Spam. Workspace rules can quarantine or reroute mail before the user sees it.
Gmail search results for a sender address and unique test subject.
Search across the whole mailbox with in:anywhere from:sender@example.com subject:"plain text test". The in:anywhere operator includes Spam and Trash. If you have the Message-ID from a message copy or Workspace Email Log Search, use in:anywhere rfc822msgid:unique-id@example.com to find the exact message. The Message-ID is available under More > Show original. For send-as mail, search the actual From address; if no result appears, remove the sender and subject restrictions.
- A fresh message can appear inside an older thread instead of at the top as a separate email.
- Open Settings > See all settings > Filters and blocked addresses. Review rules that skip the Inbox or delete messages.
- A blocked sender's messages go to Spam. Unblock an intended sender in Filters and blocked addresses, and mark a legitimate message in Spam as "Not spam".
- Gmail normally keeps messages sent to your own alias or a Google Group you belong to in Sent or All Mail, without a separate Inbox copy. Check those locations, Group delivery settings, and Workspace logs before treating this self-test as a delivery failure.
- When Google Account storage is full, Gmail cannot send or receive mail. Storage is shared with Google Drive and Google Photos; Spam and Trash also use space. After freeing storage, ask the sender to resend rejected messages.
- Review Settings > See all settings > Forwarding and POP/IMAP, or Forwarding. Check whether forwarding or a connected mail client archives or deletes Gmail's copy; choose "Keep Gmail's copy in the Inbox" when appropriate.
- Compliance, routing, quarantine, and group moderation rules can hide the message from the end user.
A recipient-side issue becomes more likely when two different senders fail only for the same recipient or the same recipient domain. That pattern points away from the sender's account and toward the recipient mailbox, group, domain, or admin policy. Google's missing-message troubleshooting includes these filter and forwarding checks.
Sender-side causes when there is no bounce
A sender-side issue becomes more likely when one sender fails across multiple recipients. In personal Gmail, check web Gmail's Sent folder, Drafts, Scheduled, Outbox, account warnings, storage, and Settings > Accounts and Import > Send mail as. In Workspace, also check whether the sender is an alias, delegated mailbox, group, or application.
Normal Gmail compose
- A sent copy with the exact recipient and timestamp is the starting evidence, rather than proof of delivery.
- Gmail can hold a message in Outbox while offline. Reconnect and confirm it appears in web Gmail's Sent folder.
- A plain text retest separates message content from account or routing trouble.
- Retest at mail.google.com or in the Gmail app. Success there points to a third-party client, browser extension, or mobile sync problem.
Gmail API or send-as
- An accepted API request is not the same as a human-visible inbox result.
- Programmatic Gmail sending is subject to quota, app, and abuse checks.
- Inspect headers for send-as, aliases, and delegated accounts to confirm the actual sending identity and service.
- For a custom send-as identity, confirm address verification and outgoing SMTP credentials. If replies are missing, also check the Reply-To address.
When an app is involved, collect the full HTTP response, Gmail API message ID, sending account, OAuth scopes, and app error logs. Google's Gmail API error documentation explains that daily sending limits are shared across API and other Gmail clients. After a limit is reached, HTTP 429 errors can take several minutes to appear, so HTTP 200 alone does not prove a message was sent. Record the Internet Message-ID separately for mailbox searches.
For personal Gmail, Google's sending limits include more than 500 emails in a day or more than 500 recipients in one message. After a sending-limit error, sending normally resumes within 1 to 24 hours. Check the exact warning and wait before retesting. Workspace accounts have different limits.
Google's send-as guidance says consumer Gmail will stop supporting "Send mail as" for third-party addresses in January 2027. Google Workspace send-as functionality and other Gmail addresses you own are unaffected. Google's transition timeline says existing third-party configurations continue working during the transition, with restrictions on new configurations. Plan a replacement for an affected sending path; the future removal does not itself explain a failed send in 2026.
Check custom-domain routing and authentication
If the address is name@example.org and the user reads it in Gmail, it is a custom-domain address. Gmail is the interface, but the mailbox or outbound SMTP service is not necessarily Google Workspace. Check recipient MX for incoming routing, then confirm the sender's actual path before reviewing SPF, DKIM, DMARC, and any Workspace routing or quarantine rules.
Use Suped's domain health checker to inspect published email authentication records. For DKIM, use the selector and signing domain from the message or sender configuration. DNS checks need to be compared with the received message's authentication results to establish a sending problem.
Domain health checker sample results showing DMARC, SPF, DKIM scorecards and detailed validation checks
Authentication matters only after the path is clear
For personal @gmail.com sending, SPF, DKIM, and DMARC are Google-managed. For a custom domain, DMARC requires SPF or DKIM to pass with an authenticated domain that matches the visible From domain under DMARC's domain-matching rules. A valid DNS record alone does not prove a message passes authentication. Google's authentication requirements explain the checks.
Example starter DMARC recorddns
Host: _dmarc.example.org Type: TXT Value: v=DMARC1; p=none; rua=mailto:dmarc@example.org
This DMARC record is an example for a domain you control. Replace the domain and reporting mailbox with real values, and make sure that mailbox receives reports. The p=none policy requests no DMARC enforcement; it does not repair authentication or guarantee inbox delivery. Do not replace an existing enforced policy to troubleshoot one missing message.
Authentication and reputation checks that matter
Authentication checks matter most when the sender uses a custom From domain. In a received Gmail test, open More > Show original to inspect SPF, DKIM, DMARC, and the visible From domain. Suped's email tester can inspect a separate test sent through the same sending path. Compare those results with Gmail's received headers when a copy is available.
Email tester
Send a real email to this address. Suped shows a results button when the test is ready.
?/43tests passed
For ongoing domain operations, Suped's DMARC monitoring product connects authentication results with source identification and policy staging. Use it to identify failing sending sources before changing a domain's policy. Aggregate DMARC reports do not confirm whether an individual message reached an Inbox.
Reputation still belongs in the review for custom domains and shared sending infrastructure. Suped's blocklist monitoring checks domain and IP listings across blocklists (blacklists). A listing is a reputation clue, rather than proof of why Gmail handled one message; a clean result does not guarantee delivery.
How much evidence is enough
Use the evidence level to decide whether to keep testing mailboxes or move into domain repair.
Low confidence
Do basic triage
No Sent copy, no recipient search, no provider check.
Medium confidence
Verify routing and headers
Sent copy exists and recipient search is done, but the receiving route or outbound service is unclear.
High confidence
Fix that side
Provider path, headers, logs, and repeat tests point to the same side.
What evidence to collect
A vague report like "it did not arrive" wastes time. Ask for a small evidence pack from the sender and recipient, then compare timestamps. If Workspace is involved, add admin logs to the pack.
- Collect the Sent screenshot, timestamp with time zone, expanded recipient address, subject, and sending app. Include the Internet Message-ID from Show original when available.
- Collect the in:anywhere search results, filter and blocked-sender settings, forwarding rules, storage status, and whether the message appears in web Gmail.
- Collect Workspace Email Log Search results, Message-ID, quarantine status, group moderation state, and routing policy hits. For messages older than 30 days, both Message-ID and recipient details are needed to check mailbox status; full delivery logs are unavailable. See Google's log-search guidance.
- Collect MX records, SPF, DKIM, DMARC, the sending source, and a header sample from a successful test.
The decision rule
If a personal Gmail sender's plain text test reaches other Gmail recipients, focus next on the affected recipient's search results, storage, and mailbox controls. Compare web Gmail with the app before escalating. For Workspace, use Email Log Search; for a custom From domain, compare authentication results and routing evidence before changing policy.
Views from the trenches
Best practices
Confirm the sender, recipient, time, and Message ID before changing any DNS setting.
Use recipient-domain MX records to identify incoming routing, then verify sender headers.
Test a plain text message first, then add links or attachments back one item at a time.
Common pitfalls
Assuming every .org address uses Gmail hides routing, filtering, and admin policy issues.
Treating no bounce as proof of delivery misses quarantine, retry, and filtering outcomes.
Changing DMARC policy during a user-to-user issue creates noise without fixing Gmail.
Expert tips
Ask the recipient to search All Mail, Spam, Trash, and filters before blaming sending.
If Gmail API sending is involved, check app permissions, quotas, and abuse controls first.
For Workspace domains, Email Log Search gives the clearest routing evidence for delivery.
Marketer view
Marketer from Email Geeks says API-based Gmail sending deserves separate review because abuse controls can affect programmatic mail differently than web Gmail.
2024-02-26 - Email Geeks
Marketer view
Marketer from Email Geeks says repeatability matters; a one-off failure without a bounce should be reproduced before changing DNS.
2024-02-26 - Email Geeks
When to escalate a missing message
If a fresh test is in web Gmail's Sent folder but the recipient cannot find it with in:anywhere, preserve the timestamp, exact addresses, subject, and Message-ID. For a personal Gmail account, use Gmail's Help menu or support community. For Workspace, ask the administrator to investigate Email Log Search and escalate with the log results. Include repeat-test outcomes and any delayed bounce; DNS or DMARC policy changes need evidence of a domain authentication problem.
