Product Decisions This Supports

Platform upgrade planning: v2.0.0 hard-depends on Acorn v6 / Laravel 13 and PHP >=8.3, so adopting it is effectively a decision to align the mail layer with the broader Acorn/Laravel upgrade. Teams not ready should pin v1.0.4.
Transactional email reliability: The bug fix addresses MAIL_SCHEME being silently ignored, which broke SSL delivery on port 465. This supports prioritizing email deliverability risk in release planning, especially for password resets, order confirmations, and other critical flows.
Build vs. buy: This is thin infrastructure glue that maps environment configuration to Laravel mail settings. Adopting it avoids maintaining custom env-to-mail-config compatibility code across Acorn/Laravel versions.
Roadmap and migration scope: The release creates concrete migration work: rename MAIL_ENCRYPTION to MAIL_SCHEME, audit any published config/mail.php, update deployment secrets and .env templates, and regression-test SMTP delivery.
Use cases: Roots/Sage/Acorn-based WordPress sites or Laravel apps that need framework-consistent SMTP configuration; agencies managing multiple sites with env-driven mail settings; teams standardizing on Laravel 13 conventions.

When to Consider This Package

You are on Roots Acorn/Sage and want mail configuration to follow Laravel conventions, particularly the newer scheme-based SMTP configuration.
You need a small, focused compatibility layer rather than a full email plugin or provider abstraction.
You can adopt Acorn v6, Laravel 13, and PHP 8.3+ now or on a known timeline.
You can coordinate the breaking env var change and re-publish or sync config/mail.php wherever it has been published.
You want the upstream fix for SMTP SSL delivery on port 465 rather than maintaining a local patch.

Look elsewhere if:

You are on Acorn <=5 or PHP <8.3; stay on v1.0.4 until the platform upgrade is scheduled.
You need a full email platform with provider APIs, logging, analytics, templates, deliverability tooling, or multi-provider routing.
You require long-term support without breaking upgrades or cannot absorb the env/config migration.
You do not control or publish mail configuration and cannot verify that the old encryption key has been removed.

Executives: This is a small dependency that keeps transactional email working after the Laravel/Acorn upgrade. v2.0.0 is a planned breaking upgrade, not a feature expansion. Budget limited migration time for environment variable changes, config republishing, and regression testing of critical email flows.
Engineering: Upgrade to v2.0.0 only alongside Acorn v6 / Laravel 13 / PHP 8.3+. Rename MAIL_ENCRYPTION to MAIL_SCHEME, re-publish or sync config/mail.php, and test SMTP SSL on port 465. If the platform upgrade is not yet scheduled, pin v1.0.4. The release’s main value is fixing MAIL_SCHEME being silently ignored, which otherwise causes SMTP SSL delivery failures.