Weave Code
Mandrill Bundle Laravel Package
hometogo/mandrill-bundle
Symfony bundle for integrating Mandrill transactional email, with simple configuration and a SwiftMailer transport for sending messages and templates through Mandrill’s API.
Swiftmailer-Mandrill integration for Symfony2
Frequently asked questions about Mandrill Bundle
- Does hometogo/mandrill-bundle work with Laravel?
- No. It is a Symfony2 bundle built around Symfony's dependency injection container and SwiftMailer transport tagging. Laravel has no bundle-loading mechanism and resolves mail through its own MailManager and transport contracts. Reusing it would require forking the transport class and discarding the bundle wiring.
- How do I install hometogo/mandrill-bundle in a Laravel project?
- You should not try to install it. Composer resolution will likely fail because the package carries PHP 5.x and 7.x constraints that conflict with modern PHP 8.2+ and Laravel 10, 11, or 12. Even if it installed, there is no Laravel service provider or bundle registration to activate it.
- Can I use this Mandrill bundle with Laravel 10 or Laravel 11?
- No. The package targets Symfony2, which reached end of life in November 2018, and it depends on SwiftMailer, which was abandoned in November 2021. Laravel 10 and 11 require modern PHP versions that are incompatible with the package's constraints. There is no supported integration path for current Laravel releases.
- What is the Laravel equivalent of hometogo/mandrill-bundle?
- There is no direct equivalent because Mandrill was folded into Mailchimp Transactional in 2016. For most Laravel apps, the simplest replacement is Laravel's built-in SMTP transport pointed at Mailchimp Transactional SMTP credentials. If you need API features such as tags or merge variables, build a small custom transport using the official mailchimp/mandrill-transactional SDK and register it with Mail::extend().
- Is hometogo/mandrill-bundle still maintained?
- No. The repository has 0 stars and 0 dependents and shows no evidence of active maintenance. Its three underlying layers, Symfony2, SwiftMailer, and standalone Mandrill, are all end-of-life. There is no security response channel or CVE triage process.
- How do I send Mandrill transactional emails in Laravel?
- Use Mailchimp Transactional, the successor to Mandrill. The lowest-effort option is to configure Laravel's mail settings with Mailchimp Transactional SMTP credentials and send through the Mail facade as usual. For advanced API options, implement Illuminate\Mail\Transport\Transport backed by the official mailchimp/mandrill-transactional SDK and register it in a service provider via Mail::extend(). Do not install this Symfony bundle for Laravel.
- Does hometogo/mandrill-bundle support Laravel's Mail facade?
- No. The package registers a SwiftMailer transport inside Symfony's service container, not a Laravel mail transport. Laravel's Mail facade resolves through MailManager, which expects an Illuminate\Mail\Transport\Transport instance. The bundle contains no bridge for that lifecycle.
- What are the alternatives to hometogo/mandrill-bundle for Laravel?
- The main alternatives are Laravel's stock SMTP transport pointed at Mailchimp Transactional, or a custom Laravel transport wrapping the official mailchimp/mandrill-transactional SDK. For simple transactional needs, SMTP is usually sufficient and requires no package. If you evaluate other Composer packages, choose ones that explicitly support Laravel 10+ and are actively maintained.
- How do I test Mandrill email sending in Laravel after migrating from this bundle?
- Use Laravel's Mail::fake() to assert that mailables are sent without hitting the provider. You can also configure the log or array mail driver in your testing environment. If you build a custom Mailchimp Transactional transport, swap it with a fake through the container in your tests. The old Symfony bundle offers no testing integration for Laravel.
- Is it safe to use hometogo/mandrill-bundle in production?
- No. The package is unmaintained, has no security disclosure process, and targets end-of-life components. It handles API keys and message content, so using it introduces supply-chain and credential-handling risk. Modern Laravel applications should use maintained SDKs or Laravel's built-in mail features instead.
Weaver
How can I help you explore Laravel packages today?