Delivery history

One timeline per mail, across every provider.

The SMTP session, the rules that held or tagged it, each provider attempt, and the delivery events that came back, in the order they happened.

Support asks why a customer never got their password reset. Search the address, open the mail, and the timeline answers: when Mailway received it, which rules matched, which provider took it and how long that took, and what the recipient's server said back. Each step keeps the provider's own response, so the answer is a quote, not a guess.

Accepted is never counted as delivered: a mail turns delivered only when the provider's delivery event says so, and a reported bounce or complaint puts the address on the suppression list for every provider in the project. Every event can also reach your own app as a signed webhook, and when a mail didn't arrive, the troubleshooting guide starts from this same timeline.

Delivery history

“Sent” is not
the whole story.

Most mailers call a mail “sent” as soon as a server answers 250, SMTP’s OK. That only means the server took the mail, not that it arrived. Mailway records the rest: every attempt, every provider response, every error code, down to the SMTP session for mail relayed over SMTP. So when support asks “did that email go out?”, you answer with a timeline.

Where a provider reports back (every supported provider except Gmail and Any SMTP server), its delivered, bounced, and complained events land in one normalized delivery history, beside every other provider's attempts and responses on the same timeline. No single provider can see across your whole sending; the gateway in front of them can.

  • Search by subject, sender, recipient, or state
  • Delivered, bounced, complained: one vocabulary for every provider that reports outcomes
  • A bounce or complaint your provider reports blocks the address for every provider in that project
  • The SMTP session behind every relayed message, credentials redacted
  • Per-project analytics, with 30 days of volume
console.mailway.net — Mailssample data
invoice to:customer@
Invoice #2041
customer@gmail.com
delivered2m
Password reset
anna@outlook.com
delivered9m
Order confirmation
old-address@fake.io
bounced14m
Weekly digest
team@company.eu
accepted22m
Shipping update
leo@proton.me
pending31m
1 match
Delivery timeline — Invoice #2041
● received via SMTP :587 09:41:02
● rule matched → tag billing
● SendGrid 535 credentials rejected → retry in 5 s
● accepted by Amazon SES · 142 ms · 09:41:07
● delivered · Amazon SES delivery event · 09:41:08
Archive

Your app doesn't have a Sent folder.
Mailway gives it one.

Every mail client keeps what you send. Your app sends the more consequential mail and keeps none of it: receipts, reset links, and contracts vanish the instant SMTP takes them. Mailway archives each message exactly as sent, searchable by sender, recipient, subject, and state. So when a customer complains and legal asks what exactly was sent to them, and when, you open the emails themselves instead of a log line that mentions them, for as long as your plan keeps them (30 days on Free, a custom window on Enterprise, up to unlimited with a retention add-on).

And it doesn't have to be a developer who looks. Give support or legal a member seat and they answer "what did we send?" themselves, only for the projects you give them.

Search a sample Sent folder →

storedthe raw message, byte-for-byte: headers, attachments, original DKIM signature intact (SMTP relays; an API send is kept as the JSON request Mailway accepted)
foundby sender, recipient, subject, plus operators like state:delivered, before:2024-06-01, rescued:yes
openedrendered · plain text · headers · raw source · attachments, unchanged for your plan's full retention
console.mailway.net — Mails
to:customer@gmail.com
Invoice #20412026-04-10✓ delivered
Payment reminder — invoice #19872026-03-12✓ delivered
Changes to our terms of service2026-01-15✓ delivered
Your password was changed2025-11-02✓ delivered
Welcome to YourApp2024-06-18✓ delivered
renderedheadersrawinvoice-2041.pdf
FromYourApp Billing <billing@yourapp.com>Tocustomer@gmail.comDateFri, 10 Apr 2026 09:41:02 +0000
Invoice #2041YourApp
Amount due · €240.00due 10 May 2026
accepted by Amazon SES 09:41:07 · deliveredsha-256 9f2c…a41e · the bytes as sent
5 of 5 sent to this customernewest first

Your mailer config has
one block to change

Mailway is in private beta, and we onboard teams one at a time. Leave your email and we'll send your invite when it's your turn.

read the docs meanwhile →

join the waitlist — mailway.net

Your invite, one email away.

Mailway is in private beta, and we onboard teams one at a time. Leave your email and your invite arrives when it's your turn.