What it does
Everything serves the send.
A bulk email tool is only as good as whether the email arrives. Mule Mail is built outward from that, not bolted onto it.
The send pipeline, written down.
No magic. When you click send, this happens, in this order, every time. The suppression check is not optional and not last.
Try it free- 01Validate the campaign, subject, and that an unsubscribe link exists
- 02Resolve recipients: union of lists, minus suppression, minus exclusions
- 03Render the template with merge data and a plain-text alternative
- 04Inject tracking and the List-Unsubscribe header (RFC 8058)
- 05Send in metered batches, retry failures with backoff
- 06Roll stats up so the dashboard reads fast
The dashboard
Four numbers an owner cares about, large and tabular.
Subscribers, sends this month, open rate, click rate. The same skeleton as the tools you know, rendered so it is calm instead of loud.
Hey, Markus
Sunday, June 25, 2026
Action needed
DKIM is not yet verified on mail.acme.co. Sends from that domain are paused until DNS resolves.
Active subscribers
8,412
Sends this month
126,540
Avg open rate
47.2%
Avg click rate
6.8%
Recent campaigns
Across every list in this workspace
May product update
Regular · Customers list
Spring re-engagement
Automation · Lapsed 90d
April newsletter
Regular · All contacts
Sends over time
Delivered volume, last 7 months
Top campaigns this month
By open rate
1st
BFBlack Friday preview
61.4%
2nd
WEWelcome email 1
58.9%
3rd
RTRestock: trail boots
54.1%
4th
QCQ1 customer survey
49.7%
A template editor with two honest modes
Drag-and-drop blocks that compile to bulletproof HTML, or a Monaco editor with live MJML preview for people who write their own. Both validate required merge tags on save. Neither makes you fight a WYSIWYG.
Contacts that behave like you expect
Lists for intent, segments for targeting. A CSV import that shows valid, invalid, duplicate, and suppressed counts before it writes anything. A suppression list every send is filtered against.
Automations you can read top to bottom
Welcome and re-engagement drips as linear sequences. Triggers on list join, form submit, tag, date, or a custom API event. Branching is in beta for when you grow into it.
Analytics that answer one question at a time
The funnel from sent to delivered to opened to clicked. Top subjects, top links, engagement by hour. Export any group of openers or bouncers as a new segment.
An API that is org-scoped and boring
Bearer keys per organisation, 60 requests a minute, a contacts and lists and campaigns surface, and HMAC-signed outgoing webhooks for delivered, opened, clicked, bounced, complained.