Setting up Mailchimp Transactional (Mandrill) as SMTP in QRACCESS
Connection details, how to get the credentials and exactly what to enter in the dashboard. Not sure which provider to pick? Start with the general SMTP guide.
Connection details
| Server (host) | smtp.mandrillapp.com |
| Ports | 587 (STARTTLS) · 465 (SSL) · 25 · 2525 |
| Username | your Mailchimp account email |
| Password | a Mandrill API key (not the “normal” Mailchimp one) |
How to get the credentials
- Mandrill is Mailchimp’s PAID transactional add-on: enable it from a Mailchimp account with a plan.
- Verify your sending domain (SPF and DKIM are mandatory in Mandrill).
- Under Settings → SMTP & API Info generate the API key that acts as the password.
What to enter in QRACCESS
In the dashboard: Settings → SMTP. Fill in Host and Port from the table above, pick the encryption to match the port (TLS for 587, SSL for 465), and enter Username and Password exactly as the table says — with some providers the “username” is a fixed word or an API key, not your email. Use a sender address on your verified domain and a recognisable sender name. Save, then use the test button with one of your own contacts before any bulk send.
Note: Convenient if you already pay for Mailchimp campaigns; otherwise any other provider on this list is better value.
Deliverability: SPF and DKIM
Whatever the provider, verify your domain and publish the SPF and DKIM records it gives you: that is the difference between the inbox and the spam folder. Always run a single test before a bulk send.
Would you like to try QRACCESS at your next event?
Create an account and start setting up your first event from the web control panel.
Control panel: https://control.qraccess.com