- Is slot/mandrill-bundle compatible with Laravel?
- No. slot/mandrill-bundle is a Symfony bundle built on a Bundle subclass, a dependency-injection Extension with a config tree, and service definitions wired into the Symfony kernel, and Laravel has no bundle-registration mechanism. There is no supported composer require and go path. The only reusable asset is the thin HTTP client logic that calls Mandrill REST endpoints, and even that must be verified as framework-free.
- Can I install slot/mandrill-bundle with Composer in a Laravel app?
- Composer may resolve it, but Laravel will not auto-register it because there is no Laravel service provider or package discovery metadata. Its constraints almost certainly cap PHP at 5.6 or 7.x and Symfony at 2.x or 3.x, so installation on Laravel 10 or 11 will hard-conflict or require ignore-platform-reqs. Forcing platform requirements is not acceptable on a transactional send path.
- Does slot/mandrill-bundle work with Laravel 10 or 11?
- No supported path exists. The bundle was built around Swift Mailer, which reached end-of-life in late 2021, while Laravel 9 and later ship Symfony Mailer with TransportInterface and TransportFactory. Any Swift-based integration is dead on arrival regardless of Laravel version. A Laravel 10 or 11 implementation would be a rewrite, not an adoption.
- How do I send Mandrill email from Laravel?
- Implement a custom MandrillTransport that implements Symfony Mailer TransportInterface and register it with Mail::extend in a service provider. Alternatively, wrap the maintained mandrill/mandrill or Mailchimp Transactional SDK behind that transport. Expect roughly 150 to 250 lines of code plus tests and sandbox validation. Do not wire the Symfony bundle DI extension or kernel boot logic into Laravel.
- Which PHP and Laravel versions does slot/mandrill-bundle support?
- The last release was 2021-01-06 with 64 stars and zero dependents, and the Composer constraints likely cap PHP at 5.6 or 7.x and Symfony at 2.x or 3.x. It probably pins Guzzle 3, 5, or 6, which conflicts with modern Guzzle 7 and PHP 8 curl deprecations. Read composer.json before estimating any work. It is not suitable for Laravel 10 or 11 without a fork.
- Is slot/mandrill-bundle still maintained?
- Maintenance risk is high. The package has a single-maintainer abandonment profile, a last release in January 2021, and no dependent packages providing ecosystem validation. Transactional email is a critical path, so depending on an abandoned Symfony bundle is unwise. Prefer a maintained SDK behind a Laravel adapter, or own a small internal transport package.
- How do I configure the Mandrill API key in Laravel?
- In Symfony the API key and transport options live in the bundle config tree. In Laravel there is no equivalent bundle config, so place the key in config/services.php and read it from the environment, for example config services.mandrill.secret. A custom transport or SDK adapter should resolve credentials from that config at send time.
- Can I use Mandrill templates with Laravel?
- Yes, Mandrill templates can be used, but not through the bundle Symfony wiring. Mandrill templates are sent via the messages/send-template endpoint with template_name and template_content, and you would expose that through a custom Laravel transport or a dedicated mailable. Decide early whether to use Mandrill-hosted templates or render Laravel Blade views and send raw HTML.
- Does slot/mandrill-bundle support Symfony Mailer or Swift Mailer?
- The bundle targets Swift Mailer, which is end-of-life. Laravel 9 and later use Symfony Mailer and its TransportInterface plus TransportFactory, so a Swift-based transport cannot plug into the current mail pipeline. Treat any Swift Mailer reference in the execution path as a blocker and remove it during a rewrite.
- What are alternatives to slot/mandrill-bundle for Laravel?
- For Laravel, wrap the official mandrill/mandrill or Mailchimp Transactional SDK in a custom transport, or implement the transport directly against messages/send and messages/send-template as a private Composer package. If provider choice is open, Postmark or Amazon SES remove this dependency risk entirely. Vendor or fork the bundle only if those options are blocked, and assign clear long-term ownership.