Your password reset emails were arriving fine for years through Mailchimp Transactional (formerly Mandrill). Last month, three customers complained that magic-link sign-ins never arrived. You checked Mandrill: status “Sent.” You checked your customers’ spam folders: nothing. You checked the rejection logs: nothing.
Welcome to the most common Mandrill / Mailchimp Transactional problem: shared sender reputation. Here’s why it happens and the simpler alternative we recommend.
What is Mailchimp Transactional?
Mailchimp Transactional is the rebranded version of Mandrill, an SMTP / API service Mailchimp acquired in 2016. It’s designed for one-to-one transactional email — password resets, order confirmations, form submission notifications, magic-link logins, abandoned cart reminders. Not the same thing as regular Mailchimp (which handles newsletter / marketing sends).
Mailchimp Transactional uses a block-based pricing model: you buy “blocks” of 25,000 emails for around $20 each. You also need an active Mailchimp Marketing plan ($13+/month) before you can use Transactional. For low-volume sites, this means a minimum cost of ~$33/month even if you’re only sending a few hundred emails.
Why Mailchimp Transactional delivery problems happen
1. Shared sender reputation
Unless you’re on a high-volume plan with a dedicated IP, your transactional sends go out from IP pools shared with thousands of other customers. When one customer’s send pattern triggers a Gmail / Outlook spam classifier — or when someone abuses the service — the whole pool’s reputation suffers. Your perfectly legitimate password reset gets junked because of someone else’s sending behavior.
2. Domain verification skipped or incomplete
Many users sign up for Mailchimp Transactional, send a few test messages successfully (because Mandrill uses its own DKIM as fallback), and never add their own DKIM CNAME record. Months later, Gmail tightens enforcement and every transactional email starts failing DMARC.
3. Block exhaustion + auto-pause
If you don’t notice that your last block of 25K is running low, sends get queued silently. Customers don’t receive password resets. You only notice when support tickets start rolling in.
The cost surprise
Diagnose your Mailchimp Transactional problem
Run these five checks:
- Mandrill dashboard outbound activity. Look at recent sends. Are they marked “Delivered” or are some “Soft Bounce” / “Hard Bounce” / “Rejected”?
- Domain verification status. Settings → Domains → check the green-check next to your sending domain. Yellow / red = unverified DKIM.
- Run mail-tester.com. Send a transactional message to the mail-tester address and read the report. Below 7/10 = delivery problem.
- Check block balance. Settings → Subaccounts and limits. Low balance = silent throttling.
- Inspect Gmail headers. “Show original” on a test send. SPF / DKIM / DMARC should all show “pass.”
Three solutions
Option 1: Stay on Mailchimp Transactional, fix domain verification
If your problem is unverified DKIM, just complete the domain verification. Settings → Domains → Add → paste the CNAME record into your DNS. Costs nothing, keeps your current Mandrill account.
Drawbacks: still on shared IPs, still locked into block-based pricing.
Option 2: Switch to SendGrid or Postmark
Both are dedicated transactional services with cleaner pricing than Mandrill. SendGrid free tier is 100 emails/day. Postmark starts at $15/month for 10K sends.
Drawbacks: SendGrid’s shared IP reputation has been declining for years; Postmark’s pricing scales fast above 10K/month.
Option 3: Switch to SecureSMTP (recommended)
Dedicated transactional infrastructure with domain-isolated sender reputation on every paid plan. Free tier for testing (100/mo). Predictable monthly pricing starts at $7/month for 2,000 emails — no blocks to buy, no Mailchimp Marketing plan required.
How to migrate to SecureSMTP
- Sign up at securessmtp.com/signup. Free tier, no card required for testing.
- Verify your sending domain. Dashboard → Domains → Add → 2 DNS records (1 TXT, 1 CNAME). Auto-verifies in minutes.
- Update SMTP credentials in your app. Replace:
# OLD (Mandrill) SMTP_HOST=smtp.mandrillapp.com SMTP_PORT=587 SMTP_USER=your-mandrill-username SMTP_PASS=your-mandrill-api-key # NEW (SecureSMTP) SMTP_HOST=smtp.securessmtp.com SMTP_PORT=587 SMTP_USER=your-securessmtp-username SMTP_PASS=your-securessmtp-password
- Deploy + test a transactional send. Verify it lands in inbox AND in SecureSMTP dashboard activity feed.
- Run both services in parallel for 1–2 weeks. Log on both sides. Verify no edge cases.
- Cancel Mailchimp Transactional + downgrade Mailchimp Marketing (if you don’t need newsletter sending).
Mailchimp Transactional vs SecureSMTP
| Feature | Mailchimp Transactional | SecureSMTP |
|---|---|---|
| Pricing model | Block-based ($20/25K) | Monthly tiers |
| Minimum cost | $33/mo (+ MC Marketing) | Free or $7/mo |
| Sender reputation | Shared IPs | Domain-isolated |
| Setup time | 1–2 hours | 5 minutes |
| Free tier | No | 100 emails/mo |
| Required other services | Mailchimp Marketing plan | None |
| Dashboard | 2 (Marketing + Transactional) | 1 |
| API simplicity | Complex (templates, merge) | Simple POST |
Frequently asked questions
What is Mailchimp Transactional, and how is it different from Mailchimp?+
Mailchimp Transactional is the rebranded version of Mandrill, an SMTP/API service Mailchimp acquired in 2016. Regular Mailchimp is for newsletters and marketing campaigns (bulk one-to-many sends). Mailchimp Transactional handles one-to-one transactional email — password resets, order confirmations, form submissions, magic links. They have separate pricing, dashboards, and APIs even though they share Mailchimp branding. Many users get confused and assume their newsletter Mailchimp plan covers transactional — it doesn't.
Why is Mailchimp Transactional expensive?+
Mailchimp Transactional uses block-based pricing — you buy "blocks" of 25,000 emails for ~$20 each. You need an active Mailchimp Marketing plan ($13+/month) just to use Mailchimp Transactional. So even for a small site sending 1,000 transactional emails/month, you're paying minimum $33/month between the two services. The pricing also doesn't cleanly scale — there are no smaller blocks for low-volume senders.
My Mailchimp Transactional emails are going to spam. What do I do?+
First, verify your sending domain in Mailchimp Transactional and add their DKIM CNAME record to your DNS. If that doesn't fix it, you're likely on a shared IP that's been blocklisted by another customer's sending behavior. Mailchimp Transactional only offers dedicated IPs on higher-volume plans. The simplest fix is to switch to a service like SecureSMTP that includes domain-isolated reputation on all paid plans.
Can I use Mailchimp Transactional + Mailchimp Marketing together?+
Yes, that's the recommended setup if you need both — transactional for confirmations + marketing for newsletters. Two separate dashboards, two billing items. SecureSMTP handles only the transactional layer (we don't do bulk newsletter sending), so if you have an active newsletter audience, you'd still need a tool like Mailchimp Marketing, Beehiiv, or Substack alongside.
How do I migrate from Mailchimp Transactional to SecureSMTP?+
Migrate in three steps: (1) Sign up for SecureSMTP and verify your sending domain (2 DNS records). (2) Update your application's SMTP credentials to point at smtp.securessmtp.com:587 with your SecureSMTP username/password instead of smtp.mandrillapp.com. (3) Test a transactional send and verify it lands in inbox. Both services use standard SMTP, so the migration is usually a 5-minute config change in your hosting environment, with no app code changes needed.
What about the API? Mandrill's API is different from SMTP.+
SecureSMTP exposes a REST API that's simpler than Mandrill's. POST to /v1/mail/send with from / to / subject / html / text fields — that's it. If you were using Mandrill's send-template endpoint with merge variables, switch to building the templated content on your end and sending the rendered HTML through our /v1/mail/send endpoint. Most apps that used the Mandrill API can swap to ours in under an hour.
Do I need to keep my Mandrill account active during migration?+
For a clean migration, keep Mandrill active for 1–2 weeks after switching, with logging on both sides. This lets you verify SecureSMTP delivery is working and catch any edge cases (oauth provider callbacks, specific recipient domain reputation, etc.) before fully cancelling Mandrill. Once you've confirmed everything works for at least one full week, cancel the Mailchimp Transactional subscription.
Ready to fix it?