- Can I use symsensor/actuator-mailer-bundle in a Laravel application?
- No. It is a Symfony bundle that extends SymSensor/ActuatorBundle and depends on Symfony bundle registration, the Symfony DI container, and ActuatorBundle's health-indicator contract. Laravel uses service providers and a different container lifecycle, so the package cannot be dropped into a Laravel app. Sharing PHP and symfony/mailer is not enough to make the health-check wiring portable.
- What does symsensor/actuator-mailer-bundle actually do?
- It extends the ActuatorBundle with mailer diagnostics, adding health checks for the Symfony Mailer component to actuator endpoints. It registers a health indicator that probes transport and delivery health so ops and monitoring tooling get visibility. It is an early-stage package with minimal observed adoption, so review the source before relying on it.
- How do I install symsensor/actuator-mailer-bundle?
- Install it with Composer in a Symfony application that already runs symsensor/actuator-bundle, then register the bundle in config/bundles.php. Configure your mailer transport as usual and the ActuatorBundle health endpoint will discover the indicator. Only take this route if ActuatorBundle is already a platform standard for you.
- Does it work with Laravel's mail transports like smtp, ses, postmark, log, or array?
- Expect it to cover Symfony Mailer transports only, since the health wiring is bound to Symfony's bundle and DI stack. Laravel does use symfony/mailer under the hood for several transports, but that does not make this bundle's indicator usable in Laravel. Verify against the source before assuming parity for any specific transport.
- What are the risks of wiring mailer health checks into a readiness probe?
- Live SMTP or API probes can block, time out, or trip provider rate limits. Worse, if mail is a secondary integration, a degraded email dependency could pull your application out of rotation and cause an outage. Keep mail diagnostics out of gating readiness checks and run them as separate, low-frequency monitoring instead.
- Is symsensor/actuator-mailer-bundle production ready and actively maintained?
- The signals are poor: 0 stars, 0 dependents, last release 2023-12-06, and no visible maintainer cadence, security response, or compatibility testing. It is effectively unproven in production anywhere observable. If you adopt it, be prepared to fork it and own maintenance yourself.
- What is the Laravel alternative for health checking the mailer?
- Build a native Laravel health check: a custom /health or /healthz route, optionally using spatie/laravel-health, that validates mailer configuration and performs a lightweight, bounded transport probe if needed. Treat this bundle as a reference implementation and port the useful logic rather than installing it. That keeps the check inside Laravel's container and lifecycle.
- Does a passing mailer health check guarantee email deliverability?
- No. A successful transport connection only shows the transport is reachable with the current credentials; it says nothing about deliverability, queue health, bounce processing, or sender reputation. Treat the result as a narrow connectivity signal, not proof that mail is being delivered. This semantic gap is a known risk with mailer health checks generally.
- What Symfony and PHP versions does symsensor/actuator-mailer-bundle require?
- Compatibility must be verified directly in the package's composer.json: check the declared PHP constraint, supported Symfony versions, and which symsensor/actuator-bundle release it needs. Also confirm whether that underlying bundle is itself maintained. Given the 2023 release date, expect constraints may lag current runtimes, so run a spike in a disposable Symfony app first.
- How would I port this package's health check to Laravel?
- Reimplement the indicator against Laravel's mail manager: resolve the configured default mailer, validate the transport settings, and optionally perform a short-timeout, low-frequency probe. Wrap it in your own health route or a package like spatie/laravel-health. There is no migration path from this bundle because no working Laravel integration exists to migrate from.