- Is hipaway-travel/mandrill-bundle a Laravel package?
- No. It is a Symfony bundle that registers through bundles.php or AppKernel and relies on Symfony's DependencyInjection Extension, Configuration tree, and YAML/XML service definitions. Laravel has no bundle loader and only consumes Symfony components, so there is no supported drop-in path. Treat it as a Symfony-only package when evaluating it for a Laravel application.
- How do I install MandrillBundle in a Laravel application?
- You cannot install it as a native Laravel package; Composer may pull it in, but Laravel will not register the bundle or load its services. Its composer.json likely pins PHP 7.x-era constraints and symfony/* ^3 or ^4, which conflict with illuminate/* in current Laravel versions. Run composer why-not against your target Laravel release before attempting anything. A small wrapper around the mailchimp/transactional SDK is the realistic path.
- Does MandrillBundle support Laravel 10 or Laravel 11?
- No. The bundle predates Laravel 9's move to Symfony Mailer and was last released in January 2021 under a single maintainer organization. Its constraints target older Symfony majors, so Composer resolution against Laravel 10 or 11 will almost certainly fail. Even if it installed, Laravel has no bundle registration mechanism to boot it.
- Can I use MandrillBundle's Swiftmailer transport with Laravel 9 and later?
- No. Bundles of this vintage typically decorate swiftmailer.mailer, and Swiftmailer reached end of life in November 2021. Laravel 9 and later use Symfony Mailer, so that hook targets an abstraction Laravel no longer uses. You would have to rewrite the transport rather than reuse it.
- How do I send Mandrill transactional email from Laravel without this bundle?
- For plain transactional delivery, configure Laravel's built-in mailer: set MAIL_MAILER=smtp, MAIL_HOST=smtp.mandrillapp.com, MAIL_PORT=587, the username to your Mandrill account, and the password to your Mandrill API key. That requires no extra dependency and covers password resets, receipts, and notifications. Use the API only when you need templates, merge variables, tags, scheduling, inbound, or webhooks.
- What is the best alternative to MandrillBundle for Laravel?
- Use the officially maintained mailchimp/transactional SDK behind a small Laravel service provider, roughly 150 lines, registering a singleton client and publishing a config file. Keep Mailable classes for rendering and call the SDK for template and tag features. That is cheaper, safer, and more legible to your team than porting Symfony bundle internals.
- What PHP and Laravel versions are compatible with MandrillBundle?
- Assume PHP 7-era code until proven otherwise. The bundle's Composer constraints most likely pin PHP 7.x and symfony/* ^3 or ^4, and its test suite and CI predate PHP 8.2 and 8.3. Check composer.json and run composer why-not against your target Laravel version early, because those constraints will drag EOL Symfony packages into your dependency graph.
- Is MandrillBundle maintained and safe for production?
- It has a single maintainer organization, 64 stars, zero dependents, and a last release in January 2021, so there is no field validation anywhere. The MIT license is permissive, but there is no visible security disclosure process. The Mandrill v1 API itself is stable and still operated, so the upstream service is not the risk; the PHP package is.
- How do I test a Mandrill integration in Laravel?
- Start with a one-day spike: send one plain SMTP message and one template message through the SDK, and measure deliverability against your current baseline. Then validate webhook signature verification and suppression-list handling, since that is where the real complexity lives. Fake the client in feature tests with Laravel's container bindings or HTTP fakes so tests never hit the live API.
- Should I fork MandrillBundle to use it with Laravel?
- Only if a specific abstraction inside it is load-bearing for you. The reusable surface is thin, essentially a config/DTO layer and a wrapper around Mandrill's REST v1 endpoints, which the mailchimp/transactional SDK already covers with modern PHP support. Forking also means owning a CI matrix across supported PHP versions and a dead Swiftmailer path, so a vendor fork is hard to justify.