Send WordPress email through Mandrill
Mandrill is Mailchimp’s transactional email service, a natural fit for sites that already run their marketing on Mailchimp and want receipts and notifications in the same place.
- SMTP, through Custom SMTP
How BooleanSMTP sends through Mandrill
Through the Custom SMTP connection
In BooleanSMTP, add a mailer, choose Custom SMTP, and enter Mandrill’s SMTP server below with your Mandrill SMTP login. Logging, the fallback, retries and alerts work exactly as they do for every other connection.
| SMTP host | Port | Encryption |
|---|---|---|
| smtp.mandrillapp.com | 587 | TLS |
| smtp.mandrillapp.com | 2525 | TLS |
| smtp.mandrillapp.com | 465 | SSL |
- Username
- Any name; Mandrill does not check it (your account’s email is the usual choice)
- Password
- A Mandrill API key (Mailchimp Transactional → Settings)
Checked against Mandrill’s SMTP documentation.
Before you connect
Enable Transactional Email on your Mailchimp account, verify your sending domain in Mandrill, and create an API key to use as the SMTP password.
Setup guide: Custom SMTP connectionsPair it with a fallback
A second provider as the fallback keeps your site sending if the Mandrill add-on or key changes.
When Mandrill refuses a message, BooleanSMTP tries your fallback connection at once, logs which one delivered it, and alerts you on Slack, Discord or Telegram only if every attempt fails. See the whole path
What Mandrill receives
Only what sending needs: each message (recipients, subject, body, headers, attachments) and the credentials you enter for the connection, sent to Mandrill when WordPress sends an email. BooleanSMTP stores those credentials encrypted in your own database. Read Mandrill’s terms and privacy policy.