Weave Code
Swiftmailer Bundle Laravel Package
kunstmaan/swiftmailer-bundle
Legacy Symfony bundle that integrates the Swiftmailer mailer library. Largely obsolete now that Swiftmailer is abandoned and Symfony Mailer is the standard, so it suits only older projects still relying on Swiftmailer.
Kunstmaan SwiftMailerBundle integrates the Swift Mailer library into Symfony applications, providing a configured mailer service, transport setup, and mailer-related tooling through the framework's bundle system. It is a Kunstmaan-maintained package intended for projects that rely on the classic Swift Mailer stack.
- Configurable mailer transports (SMTP, sendmail, mail) via bundle configuration
- Swift Mailer service wiring for controllers and services
- Support for plugins and message spooling
- Symfony profiler/data collector integration for sent mail
- Maintained as part of the Kunstmaan bundle ecosystem
Frequently asked questions about Swiftmailer Bundle
- What is kunstmaan/swiftmailer-bundle and what does it actually do?
- It is a Symfony bundle from Kunstmaan that integrates Swiftmailer into a Symfony application. It ships a DependencyInjection extension, a configuration tree, and service definitions that wire a Swift_Mailer instance, transport, spool, and optional plugins such as logger, anti-flood, and redirecting into the Symfony container. It is not a Laravel package and contains no Laravel service provider.
- Can I install kunstmaan/swiftmailer-bundle in a Laravel application?
- No. Composer may resolve the package, but nothing will happen at runtime because Laravel does not load Symfony bundles or read Resources/config YAML service definitions. Making it work would mean hand-porting the YAML definitions into a Laravel service provider, at which point you are rewriting the package rather than using it. Treat it as a removal candidate for Laravel projects.
- Why isn't this Symfony bundle compatible with Laravel's service container?
- Laravel's container is PSR-11 compatible, but it ignores Symfony's Extension and CompilerPass conventions, bundle registration via bundles.php, and the Resources/config YAML loading that this package relies on. The bundle's entire value is in those Symfony-specific wiring contracts. Without a bundle loader, the service definitions are never consumed.
- Is kunstmaan/swiftmailer-bundle still maintained or abandoned?
- It is effectively abandoned. The repository is archived as of 2022-11-20, the last release is dated 2022-11-20, and it has zero stars and zero dependents. Upstream Swiftmailer itself was abandoned in November 2021 in favour of Symfony Mailer, and Symfony's own swiftmailer-bundle was deprecated and removed. This profile looks like a vendor republishing an internal fork to keep a legacy constraint installable.
- Did Laravel ever use Swiftmailer, and is this bundle the integration point?
- Laravel 8 and earlier used swiftmailer/swiftmailer directly through the framework's own mail layer, not through this Symfony bundle. Since Laravel 9, the mail layer is built on symfony/mailer. So even in the legacy case, this package was never the integration point for Laravel.
- What should Laravel developers use instead of Swiftmailer and this bundle?
- Use Laravel's native Mail facade and Mailable classes backed by symfony/mailer, which is the supported path on Laravel 9 and later. Configure a first-party transport such as SES, Postmark, Mailgun, or SMTP in config/mail.php. That replaces both Swiftmailer and any Symfony bundle wiring.
- How do I migrate a Laravel app off Swiftmailer and this bundle?
- Start with an inventory: run composer why kunstmaan/swiftmailer-bundle and composer why swiftmailer/swiftmailer, grep for Swift_ symbols and swiftmailer.* config keys, and check config/bundles.php if any Symfony-style registration exists. Classify each hit as config-only, direct API usage, or plugin dependency. Rewrite transport and mailer service definitions as a Laravel mail config block, map Swiftmailer message construction to Mailable classes, and replace spool with a queue driver and redirecting with Mail::alwaysTo(). Verify against a staging SMTP sink before cutting over.
- How do I check whether kunstmaan/swiftmailer-bundle is in my dependency graph?
- Run composer why kunstmaan/swiftmailer-bundle and composer why swiftmailer/swiftmailer to see what pulls it in, and inspect composer.lock for stale entries. Search the codebase for Swift_ symbols, swiftmailer.* configuration keys, and bundle registration files. If nothing requires it transitively and no application code touches Swiftmailer APIs, it is likely just a stale lock entry you can remove.
- Are Swiftmailer plugins like spool, logger, anti-flood, and redirecting available in Laravel?
- There is no drop-in equivalent, so each needs an explicit design decision. Spool maps to a Laravel queue driver, logging maps to Laravel's mail events and logging channels, anti-flood maps to rate limiting or throttling middleware, and redirecting maps to Mail::alwaysTo() for staging or test environments. Plan these conversions as part of the migration rather than expecting them to carry over.
- Does this bundle support PHP 8.2, PHP 8.3, and current Symfony, and is it safe in production?
- There are no compatibility releases for PHP 8.2 or 8.3 and no updates for current Symfony versions, because the package has had no release since 2022-11-20 and has no issue triage or security response surface. Keeping unmaintained mail transport code in production is a security and deliverability liability: there is no CVE intake for the Swiftmailer stack, TLS and SMTP AUTH paths will not be revisited as providers tighten requirements, and PHP deprecation drift can cause silent failures during transport construction. For Laravel, the answer is to remove it and use symfony/mailer through Laravel's Mail facade.
Weaver
How can I help you explore Laravel packages today?