- Can I use this bundle with Laravel, or is it only for Symfony?
- This bundle is designed for Symfony, not Laravel. Laravel uses its own SwiftMailer integration, and the bundle’s `AppKernel.php` registration won’t work directly. For Laravel, consider using the Mandrill API directly via Guzzle or a Laravel-specific wrapper like `spatie/laravel-mandrill`.
- What Laravel versions does this bundle support?
- This bundle doesn’t natively support Laravel—it’s built for Symfony 2/3. However, if you’re using Laravel with Symfony components (e.g., via `symfony/swiftmailer-bundle`), you could theoretically integrate it, but compatibility isn’t guaranteed. Laravel’s built-in SwiftMailer is the safer path.
- How do I set up async email sending with Mandrill in Laravel?
- Since this bundle isn’t Laravel-native, async support requires a workaround. For Laravel, use queue workers with `Mail::later()` or a package like `spatie/laravel-queueable-mail`. The bundle’s `async: true` config won’t apply directly—you’d need to adapt Mandrill’s API calls to Laravel’s queue system.
- Is this bundle compatible with Laravel’s Mail facade or SwiftMailer?
- No, this bundle isn’t Laravel-compatible. Laravel’s `Mail` facade uses its own SwiftMailer integration, which differs from Symfony’s `swiftmailer-bundle`. For Mandrill in Laravel, use the API directly (e.g., `Mandrill::messages()->send()`) or a Laravel wrapper like `spatie/laravel-mandrill`.
- What happens if I switch from Mandrill to Mailchimp’s Transactional Email?
- This bundle won’t work with Mailchimp’s API—it’s tied to Mandrill’s deprecated endpoint. You’d need to replace it with Mailchimp’s PHP SDK or a Laravel-compatible solution like `mailchimp/mailchimp-marketing-php`. The bundle’s last update (2019) reflects Mandrill’s shutdown.
- Can I use this bundle with Laravel’s Horizon for queueing Mandrill emails?
- No, this bundle isn’t Laravel-compatible, so Horizon won’t integrate with it. For Laravel, queue Mandrill emails by dispatching jobs with `Mail::to()->send()` and processing them via Horizon. Use the Mandrill API directly in your job’s `handle()` method.
- Does this bundle support Laravel’s notification system for Mandrill emails?
- No, this bundle is for Symfony only. Laravel’s notification system uses its own SwiftMailer setup. To send Mandrill emails via Laravel notifications, extend the `Mailable` class and use the Mandrill API (e.g., `Mandrill::messages()->send()`) in the `build()` method.
- Are there alternatives for sending Mandrill emails in Laravel without Symfony?
- Yes. Use the official Mandrill API with Guzzle (e.g., `Mandrill::messages()->send()`) or Laravel packages like `spatie/laravel-mandrill`, which wrap the API for Laravel’s `Mail` facade. These avoid Symfony dependencies entirely.
- How do I configure a fallback SMTP transport if Mandrill fails in Laravel?
- This bundle doesn’t support fallbacks. In Laravel, configure SwiftMailer’s `transport` in `.env` (e.g., `MAIL_MAILER=smtp`) and use `MAIL_FALLBACK_TRANSPORT=sendmail` for redundancy. For Mandrill, implement retries in your job’s `handle()` method with Guzzle’s middleware.
- Will this bundle work with Laravel’s first-party Mailables and templates?
- No, this bundle is Symfony-only. Laravel’s Mailables use Blade templates and its own SwiftMailer setup. For Mandrill in Laravel, manually render templates in your `Mailable` class and send via the Mandrill API (e.g., `Mandrill::messages()->template()`).