Weave Code
Code Weaver
Helps Laravel developers discover, compare, and choose open-source packages. See popularity, security, maintainers, and scores at a glance to make better decisions.
Feedback
Share your thoughts, report bugs, or suggest improvements.
Subject
Message
Mailchimp Mailer

Mailchimp Mailer Laravel Package

symfony/mailchimp-mailer

Symfony Mailer transport for Mailchimp/Mandrill. Send email via Mandrill using SMTP, HTTPS or API DSNs (mandrill+smtp/https/api). Configure with your Mailchimp API key for easy integration in Symfony apps.

View on GitHub
Deep Wiki
Context7

Symfony Mailchimp Mailer Bridge

Frequently asked questions about Mailchimp Mailer
Can I use symfony/mailchimp-mailer in Laravel 10+ without Symfony dependencies?
Yes, but indirectly. While the package relies on Symfony components, Laravel’s Http facade can interface with Symfony’s HttpClient. Abstract the dependency by wrapping the MailerInterface in a Laravel service provider, as shown in the example. This avoids direct Symfony inclusion in your project.
How do I configure Mailchimp/Mandrill in Laravel’s `.env` for SMTP transport?
Use the DSN format `MAIL_MAILER=mandrill+smtp://USERNAME:PASSWORD@default` in your `.env`. Replace `USERNAME` and `PASSWORD` with your Mandrill SMTP credentials. Ensure your Laravel `config/mail.php` sets the `dsn` key to match this format for seamless integration.
Does this package fix issues with inline images in Mandrill emails (e.g., logos in receipts)?
Yes, version 8.1.1 includes fixes for Mandrill’s Content-ID handling, which resolves rendering problems with inline images. Test your templates post-update, especially if they rely on embedded assets like logos or buttons, to confirm the fix works for your use case.
Is there a performance impact when sending high-volume emails via Mailchimp API?
The package itself is lightweight, but API rate limits apply. For high-volume emails, use Laravel queues to batch operations and cache API responses. Monitor performance by benchmarking API calls against SMTP/HTTPS transports, as the latter may offer better throughput for bulk sends.
How do I handle Mailchimp webhooks in Laravel with this package?
Laravel’s event system or queues can process webhooks asynchronously. Use Horizon or Broadcast to handle real-time events. No changes were made to webhook support in v8.1.1, so existing workflows remain valid. Ensure your webhook endpoint validates payloads and logs errors for debugging.
What Laravel versions officially support symfony/mailchimp-mailer?
The package is PSR-compliant and works with Laravel 8.x and later, though Symfony dependencies require careful abstraction. Laravel 10+ users should verify compatibility by testing the MailerInterface integration in their service providers. No version-specific breaking changes exist in v8.1.1.
Can I use this for multi-tenant Laravel apps with Mailchimp subaccounts?
Yes, the package supports subaccounts via the `default` transport alias. Configure each tenant’s Mailchimp API key in their respective `.env` files or use Laravel’s config caching to dynamically switch keys. This is ideal for segmented campaigns or tenant-specific email workflows.
What’s the best alternative if I only need simple transactional emails?
For basic transactional emails, consider Laravel’s native mailers like `ses` (AWS SES) or `mailgun`. These avoid Symfony dependencies and offer similar reliability. Only use `symfony/mailchimp-mailer` if you need Mandrill’s advanced features (e.g., template rendering, webhooks) or are already using Symfony components.
How do I test Mandrill email templates locally before deploying to production?
Use Laravel’s `Mail::fake()` to simulate email sends in tests. Verify inline images by embedding them with `Content-ID` in your Blade templates and checking the rendered output. For Mandrill-specific features, use the `mailchimp+api://` DSN in your test environment to validate template IDs and merge tags.
Will this package break if Mailchimp/Mandrill changes their API?
Low risk in v8.1.1, but monitor Symfony’s updates for API deprecations. Abstract package-specific logic (e.g., DSN parsing) behind Laravel interfaces to isolate changes. Test with Mailchimp’s API changelog to ensure compatibility, especially if using advanced features like subaccounts or webhooks.
Weaver

How can I help you explore Laravel packages today?

Conversation history is not saved when not logged in.
Prompt
Add packages to context
No packages found.
andydefer/laravel-cluster
testo/fiber
mintobit/jobqueue
a4sex/maintenance-bundle
a4sex/entity-date-update
a4sex/client-identifier
a4sex/base-utilites
a4sex/key-value-storage
a4sex/micro-status
chilldev/dependency-injection-extra
datinglibre/datinglibre-app-api
biberltd/corebundle
bricre/symfony-bundle-test
biberltd/logbundle
dominium/http-adapter-bundle
dominium/google-analytics
a4sex/auto-clean-entity
christhompsontldr/laravel-inky
spatie/mailcoach-vapor
spatie/laravel-javascript-views