Password resets and magic links
Time-critical messages routed on the transactional stream, never queued behind bulk mail.
Transactional email
The emails your users are waiting for.
Password resets that arrive before the user gives up. Receipts that land in the inbox, not in promotions. Alerts that show up in seconds.
Sign-up and verification
Confirm accounts quickly; DKIM-aligned mail keeps first impressions out of spam.
Receipts and invoices
Order confirmations, invoices and payment notices with attachments up to 25 MB.
Security alerts
New sign-in, 2FA codes and account changes delivered reliably.
Shipping and status updates
Event-driven notifications from your backend, queues or workflows.
Team invitations
Invites and collaboration notices that reach busy corporate inboxes.
Streams
Transactional mail gets its own lane
Every message is tagged to a stream by the credential that sends it. The transactional stream uses IP pools reserved for one-to-one mail, so bulk sending on the platform can never slow down or damage your critical messages.
- Separate IP pools per stream
- Bulk mail requires one-click unsubscribe headers
- Per-message size and recipient checks before acceptance
Streams
- transactional
- resets · receipts · alerts
- broadcast
- opt-in newsletters
- ip pools
- separate
- priority
- transactional first
Visibility
Know what happened to every message
Webhook events tell your app when something needs attention, and the dashboard shows each message from acceptance to delivery. Support teams can answer "I never got the email" in seconds.
- HMAC-signed webhook events with retries
- Delivery log with resend for webhook events
- Suppression list you can review and edit
Webhook event
- type
- message.delivered
- to
- j***@example.com
- queue id
- 4Xk9pQ2mLz
- signature
- t=…,v1=…
FAQ
Transactional email questions
What is transactional email?
Transactional emails are messages triggered by a user action or an event in your product: password resets, sign-up confirmations, receipts, invoices, shipping notifications, security alerts. They are expected, time-sensitive and one-to-one, unlike marketing newsletters sent to a list.
Why do my transactional emails go to spam?
The usual causes are missing or misaligned authentication (SPF, DKIM, DMARC), sending from a shared web host or cloud IP with poor reputation, or mixing marketing and transactional mail on the same domain and IP. MailerAce fixes the first two for you and keeps streams separate.
Should transactional and marketing email use different services?
They should at least use different IPs and ideally different subdomains, so a newsletter complaint never delays a password reset. MailerAce separates them into transactional and broadcast streams with their own IP pools.
How fast are emails delivered?
Most messages are handed to the recipient mail server within seconds. Final delivery time depends on the receiving provider; temporary deferrals are retried automatically.
Can my app know if an email bounced?
Yes. Signed webhooks notify your endpoint about delivery outcomes, so you can flag bad addresses in your own database.
Make every critical email count
Set up a domain, connect your app, and stop losing users to emails that never arrived.