Weave Code
Mail Extra Bundle Laravel Package
rezzza/mail-extra-bundle
Rezzza MailExtraBundle is a small Symfony bundle that extends the framework's mailer with extra features, making it easier to customize how outgoing email is prepared and sent in your application. Lightweight, simple to install, and easy to integrate into existing projects.
Mail tools for Swift_Mailer.
Frequently asked questions about Mail Extra Bundle
- Is rezzza/mail-extra-bundle a Laravel package?
- No. It is a Symfony bundle that decorates Swift Mailer through Symfony's dependency injection container, so none of its compiler passes or service decoration apply to Laravel's MailManager and Mailer contract. There is no Laravel service provider, facade, or config file. Adopting it in a Laravel app would require adapter work that the 2015-era codebase does not support.
- Can I install rezzza/mail-extra-bundle in a Laravel 10 or 11 application?
- Practically, no. The package was last released in December 2015 and pins Symfony 2.x/3.x-era constraints plus a swiftmailer/swiftmailer dependency, so it will not resolve cleanly against a modern Composer graph. Laravel 9 and later ship a Symfony Mailer-based transport, meaning the concrete mailer class this bundle decorates is not even present. Composer will either refuse the install or force you to downgrade the rest of your stack.
- What features does MailExtraBundle actually provide?
- It adds four things on top of the mail stack: in-browser preview of rendered messages, delivery redirection that forces all mail to a single address in dev or staging, message logging of what was sent to whom and when, and per-environment configuration so the extras only run where needed. All of it is implemented as plugins and decorators around Symfony's mailer. The bundle itself is small, only a few hundred lines of glue logic.
- How do I redirect all outgoing email to one address in Laravel?
- Use Mail::alwaysTo() in a service provider, which rewrites every recipient before the message reaches the transport. You can also set the mail.to config value or wrap it in an environment check so it only applies in local and staging. That is roughly what MailExtraBundle's redirect plugin does, in one line and with no abandoned dependency.
- How can I preview rendered emails in Laravel without MailExtraBundle?
- Run a local mail catcher such as Mailpit or MailHog and point MAIL_MAILER at its SMTP endpoint; every message is rendered and viewable in a browser UI. For template-level previews, render the Mailable from a route or use a package that exposes mail views directly. Laravel's log mailer also writes full message content to the log as a fallback.
- Is Swift Mailer still maintained?
- No. Swift Mailer reached end of life in November 2021 and was superseded by Symfony Mailer. Laravel 9 and later use Symfony Mailer under the hood, and Symfony 5.4+ no longer ships Swift Mailer with the framework. Any package depending on swiftmailer/swiftmailer inherits an unpatched, unsupported dependency.
- How do I log outgoing emails in Laravel?
- Listen for the MessageSending and MessageSent events and persist the recipient, subject, and timestamp yourself. Alternatively set MAIL_MAILER=log during development to write full message bodies to the log file. A small event listener is a genuine replacement for MailExtraBundle's logging plugin and takes minutes to write.
- What is the modern Symfony equivalent of MailExtraBundle?
- Reimplement the behaviour as an EventListener on Symfony Mailer's MessageEvent for redirect, filtering, and logging, or a MessageListener for header and recipient rewriting. Message presets map cleanly to TemplatedEmail. This is roughly a day of work for the common cases and gives you supported APIs instead of a ten-year-old plugin.
- When was rezzza/mail-extra-bundle last updated?
- The last release was on 18 December 2015, so it has gone roughly a decade without maintenance. The repository has about six stars and zero dependents, which means there is no observable production usage to borrow confidence from and no upstream responsiveness if something breaks. There is also no security patching path.
- Is it safe to run MailExtraBundle in production?
- No, and the risk is asymmetric. The worst failure mode is not a crash but silent mail suppression or misrouting: a permissively configured redirect plugin can blackhole transactional mail or point live traffic at a sink address. With no maintenance since 2015 there are no guardrails against that, and the cost of a missed password reset or invoice dwarfs the effort of reimplementing the feature.
Weaver
How can I help you explore Laravel packages today?