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 current name for Mandrill, Mailchimp’s SMTP / API service. 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 is sold in “blocks” of 25,000 emails, from $20 per block. It is an add-on to a Mailchimp Standard or Premium plan, so you pay for that plan as well, even if you only send a few hundred emails a month.
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 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 → publish the DNS records it shows. 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 transactional email services with monthly plans and no separate marketing plan required. Check their pricing pages for current limits.
Option 3: Switch to SecureSMTP (recommended)
Monthly plans with no blocks to buy and no other plan required. The Free plan includes 5,000 emails a month and 1 sending domain of your own; Starter is $7/month for 50,000 emails and adds more sending domains. SMTP and a REST API are both included.
How to migrate to SecureSMTP
- Sign up at securessmtp.com/signup. Free tier, no card required for testing.
- Add a site and verify your sending domain. Dashboard → Forms → Sites → + Add Site → “Send from my own domain”. Publish the DKIM TXT record it shows, then click Check DNS and verify (the Free plan includes 1 sending domain; paid plans can add more). Copy the site’s API key; it is shown only once and is your SMTP password.
- 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=securessmtp SMTP_PASS=your-site-api-key
- 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 | $20 block + Standard plan | Free, or $7/mo for Starter |
| Own-domain sending | Yes | All plans, 1 domain on Free |
| Free tier | No | 5,000 emails/mo |
| Required other plan | Mailchimp Standard or Premium | 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 current name for Mandrill, Mailchimp’s SMTP/API service for one-to-one email, sold as an add-on to Mailchimp plans. 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 is sold in blocks of 25,000 emails (from $20 per block), and it is an add-on to a Mailchimp Standard or Premium plan. So even a small site sending 1,000 transactional emails a month pays for a Standard plan plus one block. There are no smaller blocks, and unused emails do not roll over.
My Mailchimp Transactional emails are going to spam. What do I do?+
First, verify your sending domain in Mailchimp Transactional and publish the DNS records it gives you. Then check the headers of a test email (DKIM and DMARC should pass). If they pass and mail still goes to spam, look at your content and at bounce and complaint rates. Switching provider is one option, but fix authentication first, because that is the most common cause.
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, add a site, and verify your sending domain (one DKIM TXT record; any plan, including Free, can add a sending domain). (2) Update your application’s SMTP credentials to point at smtp.securessmtp.com:587 with username securessmtp and your site API key as the 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 short config change in your hosting environment, with no app code changes needed.
What about the API? Mandrill's API is different from SMTP.+
POST to https://securessmtp.com/api/v1/mail/send with the x-securessmtp-api-key header and a JSON body: to, subject, html or text, and optionally reply_to and from: { name } (from must be an object; we set the From address). For Mandrill templates with merge variables, either render the HTML yourself, or save a template in the SecureSMTP dashboard and send it by name with your values.
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?