Important. Mailchimp Transactional was formerly called Mandrill. Both names may appear in the interface and documentation. Maildrill and Maindrill are misspellings.
A Mailchimp account and access to Mailchimp Transactional.
A verified sending domain with DKIM and DMARC.
A Mailchimp Transactional API key for Solomono Email Service.
A test message to one recipient.
Optional: store system messages through Mandrill SMTP.
An email address you can access.
A sender address on your store domain, such as shop@your-domain.com.
Access to the domain DNS panel: registrar, hosting provider, or Cloudflare.
Administrator access to the Solomono store.
Warning. The API key is also the SMTP password. Never share it in chats or show it in screenshots.
Mailchimp Transactional is a paid add-on for Mailchimp Marketing Standard or Premium. Sending volume is purchased in monthly blocks of 25,000 emails.
Eligible new accounts may use a demo. The current interface allows sending only to addresses on your own domain, up to 25 sent emails per hour, and up to 100 received emails per hour. The official help center also states an overall demo limit of up to 500 sent emails.
Warning. In demo mode, the recipient must be on the same verified domain. For soloqa.online, test with an address such as info@soloqa.online or test@soloqa.online. Messages to Gmail, Meta.ua, mail-tester.com, and other external domains will be rejected by Mailchimp with recipient-domain-mismatch.
Open https://login.mailchimp.com/signup/.
Enter your Email, Username, and a strong Password.
Click Sign up.
Open the Mailchimp email and confirm your address.
Finish the initial profile setup using accurate company details.
.png)
Figure 1. Creating a Mailchimp account
In Mailchimp, open Automations → Transactional.
If Mailchimp offers a demo or paid option, select the required option and confirm its terms.
The Transactional page displays a three-step wizard: Create your API key, Confirm your domain, and Authenticate your domain.
.png)
Figure 2. Current Mailchimp Transactional setup wizard
Important. The Mandrill name is still used for the SMTP server and in some emails, but initial setup now takes place directly in Mailchimp.
In the first wizard step, click Create API key.
Mailchimp displays the Copy your API key dialog.
Click the copy icon and store the key in a secure location.
Click Done.
.png)
Figure 3. The API key is displayed only once
Do not close the dialog until the key is saved. Mailchimp will not display the same value again after the dialog is closed.
Warning. Use the key created by the Mailchimp Transactional wizard. A regular Mailchimp Marketing API key will not work in this integration.
Warning. If the key appears in a screenshot, chat, or public document, revoke it, create a new key, and replace it in both Solomono and SMTP settings.
Open the Confirm your domain step.
Enter a working address on the domain the store will use for sending.
For example: info@your-domain.com.
Click Send verification email.
.png)
Figure 4. Entering an address to confirm the domain
Open the message with the subject Verify your Transactional domain.
Click Verify Your Domain.
.png)
Figure 5. Domain verification email
Return to Mailchimp and confirm that Domain verified appears.
.png)
Figure 6. The domain was successfully confirmed
Important. The email address must contain the required domain. If the message does not arrive, check Spam and verify that the address was entered correctly.
Email confirmation proves that you can access an address on the domain. DNS records separately allow Mailchimp to sign the store's messages and pass recipient authentication checks.
Open Authenticate your domain and click Start authentication.
If automatic DNS connection is unavailable, Mailchimp shows the records for manual setup.
Open the registrar, hosting provider, or Cloudflare DNS panel in another tab.
Copy every record directly from the Mailchimp dialog.
.png)
Figure 7. Actual DKIM and DMARC records in the Mailchimp wizard
|
Type |
Name / Host → Value / Target |
|
CNAME |
mte1._domainkey → dkim1.mandrillapp.com |
|
CNAME |
mte2._domainkey → dkim2.mandrillapp.com |
|
TXT |
_dmarc → v=DMARC1; p=none |
|
TTL |
Default value or 3600 |
Important. Mailchimp may display the DKIM name with the full domain. Some DNS providers append the domain automatically; in that case enter only mte1._domainkey and mte2._domainkey. Check the instructions in your DNS panel.
Warning. If a DMARC record already exists, do not create a second one. Do not weaken an existing p=quarantine or p=reject policy without approval from the domain administrator.
Save the records and return to Mailchimp.
Click I’ve added these records.
Authentication may take up to 48 hours.
Result. Domain setup is complete when the wizard confirms Authenticate your domain.
.png)
Figure 8. Mailchimp Transactional is ready to use
Important. After all 3/3 steps are complete, the demo screen shows usage such as 0 of 500 emails used. The Launch App button opens the advanced Transactional/Mandrill app for activity, logs, and additional settings.
Sign in to the store administration panel.
Open Modules → SOLO Modules.
Find EMAIL_SERVICE_ENABLED.
Turn on the blue switch.
.png)
Figure 9. Email Service and SMTP modules in Solomono
Click the gear next to EMAIL_SERVICE_ENABLED or open Settings → Integrations → Email Service.
Click edit in the Email Service row.
Select Mailchimp.
Paste the key created in the first Transactional wizard step into Mailchimp API Key.
Click OK, then click the page-level Save or OK button if one appears.
.png)
Figure 10. Mailchimp API Key in Solomono
Important. Paste the key without leading or trailing spaces. Do not enter your Mailchimp account password.
Open Send Email to Customers.
Select One customer, not all customers.
Choose a test recipient.
Use a From address on the verified domain.
Add a subject and short message, then send it.
.png)
Figure 11. Safe test to one recipient
Check both Inbox and Spam.
In Mailchimp Transactional, click Launch App, then open Outbound → Activity.
Important. During the demo, the recipient must also be on the verified domain. This restriction does not apply to genuine transactional recipients on the paid add-on.
Warning. If Mailchimp Transactional → Outbound → Activity shows Rejected with Reject Reason: recipient-domain-mismatch, Solomono did reach Mailchimp. The demo plan is blocking the external recipient. Test with a recipient on the verified domain or upgrade to a paid plan.
SMTP is used for automatic store messages such as order confirmations, password resets, and administrator notifications.
In Modules → SOLO Modules, find SMTP and turn on its switch.
Click the gear or open Settings → Integrations → SMTP Settings.
Complete the fields as shown below.
|
Solomono field |
Value |
|
SMTP Username |
Mailchimp primary contact email; technically any string is accepted |
|
SMTP Password |
An active Mailchimp Transactional API key |
|
SMTP Host |
smtp.mandrillapp.com |
|
SMTP Port |
587 |
|
SMTP Security |
tls |
|
Certificate verification |
Keep its current value; change it only when instructed by support |
.png)
Figure 12. Recommended Mandrill SMTP settings in Solomono
Warning. Alternative secure combination: port 465 with ssl. Do not type ttl instead of tls.
Save the settings.
Repeat the test from section 8 and place a test order.
|
Problem |
What to check |
|
Message rejected as unsigned |
Domain is verified; both DKIM records and DMARC show green checks. |
|
Mailchimp settings do not save |
EMAIL_SERVICE_ENABLED is on; Mailchimp is selected; the Transactional wizard key is used. |
|
SMTP authentication failed |
SMTP password is an active API key, not the Mailchimp account password. |
|
Relay Access Denied |
Host is smtp.mandrillapp.com; the port is allowed; the key is active. |
|
Unable to Connect to Host |
Try 587/tls or 465/ssl; ask the hosting provider whether outbound SMTP is blocked. |
|
Demo does not send to Gmail, Meta.ua, or mail-tester.com |
This is a demo-plan restriction. Use a recipient on the verified domain or upgrade to a paid plan. |
|
Rejected: recipient-domain-mismatch |
Mailchimp received the message but rejected the external recipient domain. DNS and API may still be configured correctly. |
|
DNS does not verify |
Host names do not duplicate the domain; CNAME proxying is off; allow up to 48 hours. |
□ The Mailchimp account is confirmed.
□ Mailchimp Transactional is enabled.
□ Confirm your domain is complete.
□ Authenticate your domain is complete.
□ An active Mailchimp Transactional API key is stored securely.
□ EMAIL_SERVICE_ENABLED is on.
□ Mailchimp is selected and the API key is saved in Solomono.
□ A test email to one recipient was delivered.
□ If required, the SMTP module is on and tested.
About Mailchimp Transactional: https://mailchimp.com/help/about-transactional-email/
Add Transactional Email: https://mailchimp.com/help/add-or-remove-transactional-email/
Demo limits: https://mailchimp.com/help/transactional-email-demo/
Domain, DKIM, and DMARC: https://mailchimp.com/developer/transactional/docs/authentication-delivery/
SMTP settings: https://mailchimp.com/developer/transactional/docs/smtp-integration/
API keys: https://mailchimp.com/developer/transactional/docs/fundamentals/