Transactional Email
Transactional email is the mail your application sends in response to something a user did: receipts, order confirmations, password resets, account notices. It’s expected, one-to-one, and time-sensitive — which makes deliverability non-negotiable. A receipt in the spam folder is a support ticket; a password reset that never arrives is a lost user.
Why Mailer To Go fits transactional mail
- Speed and reliability. Transactional mail has to arrive now. Managed, monitored sending infrastructure and clean authentication keep it landing in the inbox.
- Reputation isolation. Send from a subdomain like
mtg.yourdomain.comso your critical receipts and resets are insulated from any other sending. Why we do this. - Authentication done right. SPF, DKIM, and DMARC aligned to your domain — the signals inbox providers require. How it works.
- Automatic suppression. Hard bounces and complaints are captured so you never re-send to a dead or hostile address.
Get sending
Point your app’s mailer at your SMTP credentials and send — examples in Ruby, Python, Node.js, and Go. Deploying on Heroku? See the Heroku guide.
FAQ
Is transactional email different from marketing email? Yes — it’s triggered by a user action and sent one-to-one, versus bulk campaigns. Keeping the two on separate subdomains protects your transactional reputation.
Will a subdomain change what recipients see? No. Recipients still see your root-domain From: address.
Ready? Get started.