What happened after 250 OK.
Every message gets a timeline: the SMTP session, the rules it matched, each provider attempt, and the delivery events that came back — one normalized delivery history across every provider you bring.
A provider's 250 OK only means one server accepted the handoff. Email observability is everything after: which rules matched, which provider attempt succeeded, what the provider reported back — delivered, bounced, complained — and how long each step took. Mailway records that timeline for every message, down to the raw SMTP session.
Because every provider reports back into the same gateway, those outcomes pool into one normalized delivery history — a vantage point no single provider has. An SES bounce and a Mailgun bounce read the same, outcomes are comparable side by side, and a hard bounce learned through one provider lands on the suppression list that gates them all.
The dashboard says which number it shows you: provider-accepted is not delivered, and Mailway never blurs the two. Delivery events currently flow back from Amazon SES and Mailtrap; every event can also reach your own app as a signed webhook, and the message itself stays in the archive. When a message didn't land, the troubleshooting guide starts from this same timeline.
250 OK is not
the whole story
Most providers stop at "accepted" and wish you luck. Mailway follows the message the rest of the way — every attempt, every provider response, every error code, down to the raw SMTP session. So when support asks "did that email go out?", you answer with a timeline, not a shrug.
And because every provider you use reports back into the same gateway, outcomes land in one normalized delivery history — an SES bounce and a Mailgun bounce read the same, side by side. No single provider can see across your whole sending; the gateway in front of them can.
- Search by subject, sender, recipient, or state
- Real outcomes — delivered, bounced, complained — in one vocabulary across providers
- A hard bounce learned on one provider blocks the address on all of them
- The raw SMTP session, kept for every connection
- Per-project analytics and 30-day volume
Your app doesn't have a sent folder.
Mailway gives it one.
Every mail client keeps what you send. Your app — which sends more consequential email than you do — keeps nothing: receipts, reset links, and contracts vanish the instant SMTP takes them. Mailway archives each message exactly as sent and makes it searchable like a mailbox. So when finance asks about an invoice from last March, you open the email itself — not a log line that mentions it.
Your mailer config has
one line to change
Mailway is in private beta — we onboard teams one at a time. Leave your email and we'll send your invite when it's your turn.