- Can I use henrikbjorn/stampie-bundle in a Laravel application?
- No. Despite being distributed as a PHP Composer package, stampie-bundle is a Symfony bundle: it ships a Bundle subclass and a DependencyInjection extension with a Symfony config tree, which Laravel has no equivalent for. It cannot be registered in config/app.php, cannot be picked up by Laravel's package discovery, and its services are wired through Symfony container compiler passes. In a Laravel codebase you would have to bypass the bundle entirely and instantiate the underlying Stampie\Mailer classes by hand, inheriting the dependency without any of the benefit.
- What does the Stampie Bundle actually do?
- It integrates the Stampie mailer library into Symfony and exposes a provider-agnostic email abstraction over transactional API providers such as Mailgun, SendGrid, Postmark and Mandrill. Instead of writing provider-specific HTTP calls, you inject a mailer service and send through a unified interface, swapping providers via configuration. The bundle's value is the Symfony configuration tree and DI wiring around that library.
- Is henrikbjorn/stampie-bundle still maintained?
- No. The upstream repository was archived on 30 March 2022, so there are no bug fixes, no CVE triage and no security response process. The ecosystem signal is near zero: roughly 25 stars and no dependents on Packagist, meaning essentially nobody in the public ecosystem runs it in production. Any vulnerability in the bundle, in Stampie itself or in its pinned Guzzle generation becomes your fork to fix.
- What is the Laravel equivalent of Stampie Bundle for Mailgun, SendGrid or Postmark?
- Laravel's built-in Mail system sits on top of symfony/mailer and gives you the same provider abstraction natively. Install the matching transport bridge, such as symfony/mailgun-mailer, symfony/postmark-mailer, symfony/sendgrid-mailer or symfony/amazon-mailer, and configure it in config/mail.php. You get framework-level support, active security maintenance and no third-party abstraction layer to keep alive.
- Why does composer require fail when installing stampie-bundle on Laravel 11?
- Stampie is built around Guzzle 5/6-era client interfaces, and the bundle's php and symfony/* version constraints predate modern releases. Composer resolution against Laravel 10, 11 or 12 and PHP 8.x will typically fail before runtime. Forcing it through with --ignore-platform-reqs trades a clean install for latent runtime type errors, so treat the conflict as a signal rather than an obstacle to work around.
- Does Stampie Bundle support Symfony 6 or 7 and PHP 8?
- The bundle was the idiomatic answer in the Symfony 2/3 era and has been frozen since early 2022, so its constraints target older PHP and Symfony majors. It is not a supported dependency on Symfony 6/7 or contemporary PHP versions. Even where it installs under ignore-platform-reqs, you are running unsupported code.
- Can I use the Stampie mailer classes without installing the Symfony bundle?
- Technically yes, but it defeats the purpose: the bundle is the configuration and DI wiring, so skipping it leaves you hand-instantiating mailer objects and owning the Guzzle pin yourself. You inherit the full transitive dependency chain without the abstraction the bundle was meant to deliver. Laravel Mail with an API transport gives you the same portability with framework maintenance behind it.
- How is Stampie Bundle configured?
- Configuration goes through a Symfony DI extension config tree, typically in config.yml or a Symfony config file, where you declare the provider, API key and related options for each mailer service. There is no Laravel-style config/mail.php integration and no service provider. In a Laravel app that configuration format has no consumer.
- Is it safe to run an archived email bundle in production?
- The risks concentrate in three places: no security response process for the bundle or its pinned Guzzle, frozen provider coverage that will not track API changes such as SendGrid v2 to v3 or Postmark payload revisions, and no community to absorb bugs. Zero dependents means no downstream forks carrying forward-compat patches and no Stack Overflow corpus. If a CVE lands anywhere in that chain, you own the fork.
- How do I migrate from Stampie to Laravel's Mail system?
- Replace injected Stampie mailer services with Mailables or the Mail facade, move provider credentials into config/mail.php with the appropriate Symfony transport bridge, then remove henrikbjorn/stampie-bundle from composer.json. Use Mail::fake() in tests so you can assert sends without hitting provider APIs. The migration is usually smaller than maintaining the archived dependency.