Skip to main content

Delivery events

Every message keeps a timeline of what happened to it, in order. When a send needs explaining, this is the record that explains it. A status tells you where a message ended up. The timeline tells you how it got there.

A message timeline

Open any message from Activity to see its timeline.

The events​

EventWhat triggered it
Queued for deliveryThe message was accepted by Epostix and is waiting for the relay
Accepted over SMTPYour client handed the message to Epostix over SMTP
Connected to receiving serverThe relay opened a connection to the recipient's mail server
DeliveredThe receiving server accepted the message
OpenedThe tracking pixel in the message was loaded
Link clickedA tracked link in the message was followed

Not every message shows every event. A message sent through the API has no Accepted over SMTP, and a message with tracking disabled will never record an open or a click no matter how many times it is read.

Reading the offsets​

Each event carries a time in UTC and an offset from the first event: +156ms, +43m, +2.1h. The offset is what you actually want when judging performance: the gap between the first event and Delivered is how long delivery took, and everything after that is recipient behaviour, not your infrastructure.

Delivery time varies. A gap of minutes can include queueing, throttling or a retry. A Delayed status and a retry in the timeline will tell you whether the receiving server asked us to wait.

How far to trust an open​

An open means an image in the message was loaded. That is a weaker signal than it sounds, and the timeline says so where it can.

Apple privacy proxy. Events tagged this way were produced by a proxy prefetching the image, not by a person reading the message. Apple Mail does this by default for anyone who enabled Mail Privacy Protection, which is most Apple Mail users. These opens are real events but they are not evidence anyone read anything.

Bot. Events tagged as a bot came from automated fetching. A security scanner that follows links in the message before delivering it to the recipient is the usual source. A message that shows a click within a second of delivery was almost certainly scanned, not read.

Where it can be identified, the timeline also shows the mail client, operating system, device type and IP address behind an event.

Clicks can be stronger evidence than opens, but automated scanners follow links too. Neither event alone proves that a person read the message.

When a message failed​

A failed message shows a plain-language explanation of what the receiving server said, followed by the server's verbatim response. The explanation covers the common cases.

ExplanationWhat it means
The mailbox does not existThe address is wrong or has been closed. This is a hard bounce
Rejected on content or reputation groundsThe receiving server judged the message or your sending domain, not the address
The recipient's mailbox is fullTemporary. Usually succeeds later
We could not reach the receiving serverThe recipient's mail server did not answer
The recipient's domain has no working mail serverThe domain has no usable MX record

The verbatim response is shown because receiving servers frequently include a URL explaining their own policy, and that URL is the fastest route to a fix when a large provider is rejecting your mail.

A message that never reached a receiving server has no server response. The explanation is then one of these fixed texts from Epostix.

ExplanationWhat to do
The recipient is on the suppression listNothing, unless the address was suppressed by mistake
The recipient address is invalidCorrect the address
The total attachment size exceeds the limitSend fewer or smaller attachments
An attachment could not be retrieved or has expiredCheck that the attachment URL serves the file, or upload the attachment again
The sending domain's DKIM key no longer matches its published DNS recordThe published DKIM record holds a different key. Check it in DNS health, then send again
The sending domain's DKIM record could not be found in DNSThe DKIM record was missing for as long as the message could wait. Publish it again from DNS health, then send again
Sending was paused for review beyond the maximum delivery ageSending from your workspace was held for review. Contact support if it still is
The message expired before it could be deliveredReceiving servers kept putting it off. Send again later
The message could not be sent before its delivery window ran outThe message waited longer than its delivery window. When failure.reason is sending_restricted, sending from your workspace was slowed or paused. When it is not_delivered, the cause could not be determined. Send again once sending is back to normal
The message could not be deliveredUsually a failure on the Epostix side. Send again if the message still matters

These texts can change. The API and the email.failed webhook carry the same cause as a failure object, and failure.reason is what to branch on in code.

Use has:errors in Activity to list every message that recorded an error.