Insights:What to Check First When Your Business Email Has Issues: A 5-Step Guide
Step 1: Determine the Scope of Impact
First, clarify:
- A single user or the entire company?
- Can't receive or can't send?
- All recipient domains or just one?
- Web client working but desktop client failing?
- When did it start and what was changed recently?
The scope determines the direction:
| Scope | More Likely |
|---|---|
| A single user | Client/password/capacity/rules |
| The whole company can't receive | MX/DNS/provider |
| The whole company can't send | SPF/DKIM/Tunnels/Blacklist |
| Bounce for a single domain only | Recipient policy/content/address |
Step 2: Check DNS and Authentication
dig +short MX company.com
dig +short TXT company.com
dig +short TXT selector._domainkey.company.com
dig +short TXT _dmarc.company.com
Check:
- Whether MX points to your current provider.
- Whether SPF has only one record.
- Whether DKIM resolves correctly.
- Whether DMARC policy is reasonable.
- Whether the domain has expired.
Step 3: Check Account, Capacity, and Rules
- Whether the account has been suspended.
- Whether the password has expired.
- Whether storage is full.
- Whether any forwarding rules point to invalid addresses.
Step 4: Check Logs and Bounce Messages
- SMTP response codes: 4xx for temporary, 5xx for permanent.
- The reason in the bounce message body.
- Whether rejected by the recipient's anti-spam system.
- Whether sending volume is abnormal.
- Whether flagged on a blocklist.
- Whether an account has been compromised and used for bulk sending.
Step 5: Check Client and Network
- IMAP/SMTP address and port.
- SSL/TLS settings.
- Password/authorization code.
- Firewall/proxy.
- Whether both mobile and desktop show issues.
- Test on a different network.
Common Scenarios Reference
| Symptom | Common Root Cause | First Action |
|---|---|---|
| Entire company can't receive | MX record error/domain expired | Check DNS |
| Sent emails going to spam folder | Missing authentication/content issues | Check SPF/DKIM/DMARC |
| Single user can't receive | Storage/rule/client issue | Check account |
| Overseas bounces | Channel/reputation/attachment issues | Check bounce code |
| Password correct but login fails | Authorization code/security policy | Check client settings |
Escalation and Documentation
- If unresolved within 30 minutes, escalate to the service provider.
- Record time, scope, command output, and full bounce message text.
- Back up configurations before making changes.
- Re-verify authentication and send/receive after repair.
What Not to Do
- Don't reinstall the client first.
- Don't delete logs.
- Don't change passwords for everyone to cover up the issue.
- Don't change MX without a rollback plan.
- Don't ignore bounce email body content.
Boundaries
Troubleshooting can shorten recovery time, but it cannot prevent all incidents. Daily monitoring, authentication, backups, and handoffs are what matter in the long run.
Related Reading: