Skip to main content
Track Delivery is a search interface over your server’s outgoing mail log. When someone says “I sent you an email and it didn’t arrive” or your own mail looks like it went into a black hole, this is where you check what actually happened. Open it from cPanel home → EmailTrack Delivery.
Track Delivery page with filter form and event log

What it shows

Each row is a delivery attempt. The columns tell you:
ColumnWhat it means
EventOutcome: delivered (green), deferred (yellow), bounced (red), rejected
Delivery TimeWhen the attempt happened
SenderAddress the message came from
RecipientWhere it was going
ResultServer-readable status code and the receiving server’s response message
ActionClick for the full headers and the SMTP transcript

How to read the events

  • Delivered. The receiving mail server accepted the message. Doesn’t guarantee the recipient saw it (could be in their spam folder), but the handoff worked.
  • Deferred. The receiving server is temporarily refusing. Common causes: rate limiting, greylisting, your IP not yet warmed up, the recipient’s mailbox is full. cPanel will retry on a schedule.
  • Bounced. The receiving server rejected the message permanently. The Result column tells you why: “no such user”, “blocked by policy”, “SPF check failed”, and similar.
  • Rejected. Your own server rejected the message before it even left (usually local quota or filter rules).

Filters

The form at the top narrows the search:
  • Sender or Recipient — show events for one address only
  • Time period — last hour, day, week (defaults to recent)
  • Event type — only show bounces, only show deferred, etc.
For deeper investigation, click the magnifying glass next to a row. cPanel shows the full delivery transcript: the SMTP commands and responses between your server and the receiving server. The receiving server’s response usually says exactly why a message was rejected.

Tips

  • First place to look when mail “disappears”. If the sender’s address shows successful delivery but the recipient says they didn’t get it, the message reached the receiving server. The problem is on their side: spam folder, alias misrouting, mailbox rule. Forward them the Track Delivery row as evidence.
  • Repeated deferrals. A few deferrals are normal during transient issues. Persistent deferrals (hours or days) usually mean the receiving server has flagged something about your domain. Run an Email Deliverability check to verify SPF, DKIM, and DMARC are right.
  • Bounces with “blocked” or “rejected” in the response often quote the reason. Common ones: missing or invalid SPF, missing DKIM signature, IP in a public blocklist. The Email Deliverability tool fixes most of these.

Need a hand?