Skip to content
Jooosi
Account
JM Jooosi Mail

Mandrill

Browse documentation
Overview
Contents
On this page
  1. Before you begin
  2. Supported transport and settings
  3. Create the connection
  4. Verify delivery
  5. Webhooks
  6. Troubleshooting

Mandrill (Mailchimp Transactional) supports API, HTTPS API, and SMTP delivery in Jooosi Mail. The two API schemes share the API key field; SMTP uses separate credentials.

Before you begin#

  • You need access to the provider account and the Jooosi Mail Connections screen. If the provider requires sender or domain verification, complete it in the provider account first.
  • Copy credentials directly from the provider’s own console into the matching Jooosi Mail field. Keep secret values private; never include them in screenshots or support messages.

Consult provider sending documentation for any provider-side setup requirements.

Supported transport and settings#

  • mandrill+api (default) or mandrill+https: Required: Mandrill API key (secret).
  • mandrill+smtp: Required: SMTP username and SMTP password (secret).

Create the connection#

  1. In WordPress admin, open Jooosi Mail → Connections and choose New connection.
  2. Enter a descriptive Connection name and select Mandrill in Profile.
  3. Choose the transport scheme you want to use. Enter its required fields listed above and leave fields for other schemes empty.
  4. Review the sender, routing, and advanced settings for this connection.
  5. Choose Create connection to save it.

Choose mandrill+api unless your setup specifically calls for the HTTPS variant. Jooosi Mail does not require extra endpoint settings for these schemes.

For the shared form workflow, see Connect a provider.

Verify delivery#

Use Send a test email with a recipient you control; it sends a real message through this connection. Check its status and the email log for the provider response.

Webhooks#

Mandrill webhooks can report send, deferral, bounce, delivery, rejection, click, open, spam, and unsubscribe events. Add the shared webhook secret to the connection so Jooosi Mail can validate Mandrill’s X-Mandrill-Signature HMAC. Follow Provider webhooks for the Jooosi Mail endpoint; copy the secret from Mandrill’s own console and keep its value private.

Troubleshooting#

  • For missing-field validation, confirm the scheme and fill all required settings listed above.
  • After a failed test, re-copy the matching credential and inspect the connection status and email log.
  • If an API connection fails validation, confirm the API key is in the API Key field; SMTP credentials are not interchangeable. If webhook requests are rejected, confirm the configured signing secret and X-Mandrill-Signature header are reaching WordPress.