Weave Code
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.
Symfony Mailchimp Mailer Bridge
Frequently asked questions about Mailchimp Mailer
- How do I install symfony/mailchimp-mailer in a Laravel app?
- Install it with Composer using composer require symfony/mailchimp-mailer. The package provides a Symfony Mailer transport for Mandrill, so Laravel integration usually means binding Symfony Mailer or the Mandrill transport into the container or configuring a custom mailer. Make sure your application has compatible Symfony Mailer and HttpClient components available.
- What DSN formats does symfony/mailchimp-mailer support for Mandrill?
- It supports mandrill+smtp://USERNAME:PASSWORD@default, mandrill+https://KEY@default, and mandrill+api://KEY@default. The KEY value is your Mailchimp API key. Use SMTP when you need username/password credentials, and use HTTPS or API DSNs when sending through Mailchimp API credentials.
- Can I use symfony/mailchimp-mailer with Laravel's Mail facade?
- Not directly out of the box, because Laravel's Mail facade expects Laravel mail transports rather than Symfony Mailer transports. You can bridge it by registering a custom transport or singleton that delegates to Symfony MailerInterface with the Mandrill transport. Then send through that custom service or extend your Laravel mailer configuration. The v8.1.1 release does not change this integration pattern.
- Which Laravel versions are compatible with symfony/mailchimp-mailer?
- The package is a Symfony component, so Laravel compatibility depends mainly on PHP and on the Symfony Mailer and HttpClient versions required by v8.1.1. Modern Laravel applications with compatible Symfony dependencies can integrate it, but you should check Composer constraints and test against your Laravel version. Because Laravel bundles Symfony components, version alignment is important.
- Does symfony/mailchimp-mailer support inline images in Mandrill emails?
- Yes, v8.1.1 fixes Mandrill Content-ID handling for inline images. This improves rendering for transactional templates that embed logos, buttons, or other inline assets. You should still test templates with embedded Content-ID assets to confirm they render correctly in your Mandrill workflow.
- How should I test Mandrill email sending with symfony/mailchimp-mailer in Laravel?
- Use Laravel Mail fake assertions for application-level mail behavior, and mock Symfony HttpClient or the Symfony Mailer transport for integration tests. Avoid sending real Mandrill email from CI. For template checks, test inline Content-ID images and DSN configuration with non-production credentials or a controlled test setup.
- Is symfony/mailchimp-mailer suitable for high-volume transactional email in Laravel?
- It can work for high-volume sending when you pair it with Laravel queues and explicit Mailchimp or Mandrill rate-limit handling. Batch operations should run asynchronously, and API responses should be cached where appropriate. For simple low-volume transactional email, native Laravel mailers may be simpler and lighter.
- How do I handle Mailchimp/Mandrill webhooks in Laravel with this package?
- This package provides the email transport only, so webhooks are handled separately through Laravel routes, controllers, queued jobs, or Horizon. Verify webhook payloads, log events, and use retries for reliability. The webhook workflow is unchanged in v8.1.1.
- What are alternatives to symfony/mailchimp-mailer for sending Mandrill email in Laravel?
- Alternatives include Laravel-native mailers such as Mailgun, SES, or Postmark, direct Mandrill API clients, or a custom Laravel mail transport. If your project already uses Symfony Mailer, this package is a focused Mandrill bridge. For basic transactional needs, evaluate whether the Symfony dependency and Mandrill-specific setup are worth the overhead.
- Is symfony/mailchimp-mailer maintained and safe for production Laravel use?
- It is part of the Symfony Mailchimp Mailer Bridge and v8.1.1 includes backward-compatible fixes, so production use is reasonable with normal safeguards. Monitor Symfony and Mailchimp API changes, abstract package-specific logic, and review Composer constraints during upgrades. Use queues, rate-limit controls, and webhook logging to reduce operational risk.
Weaver
How can I help you explore Laravel packages today?