Business email not working: common causes and practical checks

Determine whether the problem affects a client, identity, domain, recipient or all mail flow. Use exact SMTP responses, headers and server traces, then change one diagnosed cause at a time and verify both delivery directions.

Email faults can stop everyday business

Unanswered enquiries and interrupted workflows make email outages urgent. Common causes include missing or incorrect MX, SPF or DKIM records, full mailboxes or storage quotas, provider or server failures and misconfigured spam or security filters.

Check whether internal mail works while external delivery fails, inspect authentication settings and confirm the mail service is running. A prolonged or business-critical failure needs systematic diagnosis; improvised DNS and filter changes can make the situation worse.

First establish the failure boundary

Does the fault affect one person, one domain, one recipient or all outgoing messages? If webmail works but a local client fails, look closer to the device or profile. If several users cannot send or receive, examine service health, identity, DNS and mail flow.

Record start time, affected senders and recipients, exact errors and Message-ID. Test both incoming and outgoing directions. Make and document changes individually; simultaneous DNS, connector and client changes obscure the cause.

SMTP codes and headers provide useful evidence

SMTP 4xx responses generally describe temporary problems; 5xx indicates rejection that normally needs correction. The full message matters more than an abbreviated client display. Headers reveal the delivery path, servers, delays and SPF, DKIM and DMARC results.

Also check MX records, Autodiscover, quotas, forwarding, blocklists and transport rules. A message in spam has technically been delivered but classified differently due to reputation or content. That needs a different analysis from a connection failure to the mail server.

Demonstrate normal operation after repair

One successful message is not enough. Test internal and external recipients, with and without attachments, and inspect authentication results. For DNS changes, account for TTL and resolution from different locations. Record the cause, change and preventive action.

Monitoring certificates, DNS, queues, quotas and provider status can identify recurring problems earlier. Critical communication also needs alternative contact routes and clear escalation.

Practical checklist

01
Record scope, start time, affected accounts and exact error.
02
Test webmail, another client and both delivery directions.
03
Inspect SMTP response, message trace and complete headers.
04
Check DNS, quotas, rules, connectors and service health selectively.
05
Complete end-to-end tests and document the cause.

Frequently asked questions

Why do messages fail only for certain recipients?

Recipient filters, reputation, blocklists or different DMARC handling may be involved. The SMTP response and logs from both sides are central to narrowing the fault.

Should I immediately change DNS during an outage?

Only with evidence and a documented intended configuration. Uncoordinated MX, SPF or Autodiscover changes can create additional problems and take effect at different times because of caching.

Business email not working: common causes and practical checks

Knowledge you can put to work.