Overview

This article provides a low-risk, evidence-driven troubleshooting path for gmail cannot send email. Work from identity and service checks toward more disruptive actions, and stop before a change could cause data loss, broaden access, weaken security, or interrupt other users.

Start with the safest layerRecord the current state before changing settings. Use only approved accounts, tools, and administrative processes.

Why this happens

Google Workspace problems can originate with the signed-in account, organizational-unit policy, licensing, 2-Step Verification, storage, Gmail routing, Drive permissions, sync-client state, or a Google service issue.

Before You Begin

  • Confirm the affected organizational Google Workspace account.
  • Record the exact Gmail, Drive, 2-Step Verification, licensing, or storage error.
  • Determine whether one user or multiple users are affected.
  • Do not share credentials or weaken organization security controls.

Navigation reference: Google Admin console > Directory > Users.

Click-by-Click Troubleshooting

Step 1: Test Gmail on the web

Action: Open Gmail in a private browser window and sign in with the affected organizational Google Workspace account.

Why this matters: Web testing isolates the Gmail service/account from desktop mail clients.

What to look for: Confirm the correct account and reproduce the send/receive problem.

Expected result: You should know whether Gmail itself is affected.

Step 2: Check Spam, filters, and blocked addresses

Action: In Gmail, open Settings > See all settings and review Filters and Blocked Addresses; also check Spam and Trash.

Why this matters: Mail can be delivered but hidden, filtered, forwarded, or rejected by user settings.

What to look for: Look for rules that delete, archive, forward, or redirect expected mail.

Expected result: Unexpected user-level filtering should be identified.

Step 3: Check storage and account status

Action: Review Google Workspace storage/account status through the approved admin or user storage view.

Why this matters: Storage limits or suspended accounts can interrupt mail flow.

What to look for: Look for storage-full warnings, suspension, or service-disabled status.

Expected result: The mailbox/account should have capacity and active Gmail service.

Step 4: Run a controlled test message

Action: Send a simple plain-text test between the affected user and a known-good internal account, then repeat with an external account if appropriate.

Why this matters: Controlled tests separate inbound, outbound, internal, and external mail-flow problems.

What to look for: Record whether messages are delayed, rejected, or missing.

Expected result: The failing mail-flow direction should be identified.

Step 5: Review admin mail logs if authorized

Action: In Google Admin console > Reporting/Email Log Search or the current mail investigation view, search for the controlled message.

Why this matters: Administrative mail logs show whether Google accepted, routed, rejected, or delivered the message.

What to look for: Look for rejection reason, route, delivery status, or quarantine.

Expected result: The platform should provide a delivery outcome.

Step 6: Escalate routing, DNS, or service issues

Action: Contact IT if logs show routing/rejection problems, multiple users are affected, or domain/DNS changes may be involved.

Why this matters: Organization-wide mail settings and DNS changes can affect every user.

What to look for: Provide sender, recipient, timestamp, and message result.

Expected result: IT should have enough data for a targeted mail-flow correction.

What to Look For

  • Whether the issue affects one user/device or multiple users.
  • Whether a clean browser or alternate approved client changes the result.
  • Whether the error points to identity, permission, licensing, service, device, or network state.
  • Whether the same controlled test succeeds after the targeted correction.

When to Stop

Stop before troubleshooting becomes riskyDo not broaden access, bypass MFA/security, erase evidence, permanently delete business data, change tenant-wide settings, or perform destructive resets unless the approved IT process specifically requires it.

When to Contact IT

Contact J3 Systems Group if the issue remains unresolved, affects multiple users, requires administrator-level changes, involves security or data-loss risk, or the next step would be disruptive. Include article code KB-09.002, the affected account/device/resource, exact error, time observed, and the results of the controlled tests above.

Need help with this issue?

J3 Systems Group supports small businesses and nonprofits with Microsoft 365, Google Workspace, cybersecurity, devices, documentation, and day-to-day IT operations.

Contact J3 Systems Group

Authoritative references

Vendor interfaces, licensing, and security guidance can change. Verify current platform behavior against the primary documentation below before making high-impact production changes.

Article KB-09.002 · Review after material vendor, licensing, interface, security, or service changes.