- Does requestum/email-sender-bundle work with Laravel?
- No. It is a Symfony bundle with no Laravel surface: no service provider, no package discovery, no config publish tag, no facade, and no Laravel version constraint in its manifest. Any Laravel integration would be a hand-written port that re-derives the bundle's compiler passes and tagged services from source. Treat it as a design reference at most.
- Can I install requestum/email-sender-bundle in a Laravel app with Composer?
- A clean Composer install is unlikely to succeed. The package is tied to Symfony 4-era dependencies, while Laravel 10–12 requires PHP 8.1+ and Symfony 6/7 components, so dependency resolution is the likely first failure. There is no Laravel package discovery or config publish tag to complete the setup even if resolution passed.
- Which Laravel versions does Requestum EmailSenderBundle support?
- None. The manifest has no Laravel version constraint, and v1.0.1 added only Symfony 4 support. It does not claim compatibility with Laravel 9, 10, 11, or 12, and it provides none of the integration points those versions expect.
- Is Requestum EmailSenderBundle still maintained?
- The evidence is weak. v1.0.1 is the first sign of activity in roughly six years, and it adds exactly one line of substance: Symfony 4 support. One patch release is not a maintenance cadence, and it carries no commitment to Symfony 5/6/7 or PHP 8.1+. Abandonment risk remains high.
- What changed in Requestum EmailSenderBundle v1.0.1?
- It adds Symfony 4 support and nothing else of substance. There is no Laravel surface, no move off the Swiftmailer-era transport model, and no security process. A patch-level bump used to signal framework-version support is a semver smell worth noting.
- Does it use Symfony Mailer or modern transports?
- No. A release headlined with Symfony 4 support reads as a Swiftmailer-era integration kept nominally resolvable, not a migration to Symfony Mailer, which landed in Symfony 4.3. The package is silent on Symfony 5, 6, and 7, the versions that matter for current PHP 8.1+ applications. If it hooks the mailer, the integration point is still the one Laravel removed.
- What should Laravel developers use instead for transactional email?
- Laravel already provides queued Mailables, the database queue driver, $tries and $backoff, failed_jobs, and RateLimited job middleware. Those cover spooling, retries, and rate limiting without a third-party Symfony bundle. Pair them with your preferred mail transport provider and you get a more idiomatic result than any port of this package.
- Can I fork Requestum EmailSenderBundle and port it to Laravel?
- A fork-and-port is technically feasible but economically unattractive. The domain logic is likely a table schema, a spooler service, a send command, and a transport wrapper, and most of the work is re-implementing what Laravel already ships. The port would cost at least as much as a clean build and land less idiomatically. Start with a 1–2 day spike to inventory the API surface and confirm the license, and expect the spike to end the conversation.
- Is Requestum EmailSenderBundle safe for production?
- Risk is high. There is no advisory channel, no CVE monitoring, and no disclosure policy, and a patch release that does not mention security does not establish a security process. Symfony 4 reached end of life in November 2023, so the dependency floor is itself a liability. It is not recommended for production Laravel or Symfony applications.
- What is Requestum EmailSenderBundle actually useful for?
- Its durable value is as a design reference for a database-backed outbound mail spool with persistence, retry, and a worker command. It may also serve legacy Symfony 4 applications, though that version is EOL and adopting the package means adopting that constraint. For Laravel, use it to study the pattern, not as a dependency.