Laminas Mail Laravel Package

Product Decisions This Supports

• Legacy System Migration: Justify adoption of this package for maintaining PHP 8.4 compatibility in legacy Laravel applications where laminas/mail is still in use, avoiding costly rewrites to alternatives like Symfony Mailer.
• Email Infrastructure Consolidation: Centralize email transport logic (SMTP, Sendmail, File) under a single package to reduce technical debt and simplify maintenance.
• Compliance with SMTP Server Constraints: Leverage connection_time_limit and use_complete_quit to avoid errors with SMTP servers enforcing reuse time limits (e.g., Postfix).
• Authentication Flexibility: Support for PLAIN, LOGIN, and CRAM-MD5 authentication methods to integrate with enterprise email providers (e.g., Gmail, Exchange) without vendor lock-in.
• Roadmap for Deprecation: Align with the original laminas/mail abandonment by planning a phased migration to symfony/mailer or ddeboer/imap post-PHP 8.4 EOL.

When to Consider This Package

• Avoid if: Your team is already committed to modernizing email infrastructure (e.g., adopting Symfony Mailer or AWS SES directly). The package’s abandoned status and zero stars/dependents signal low long-term viability.
• Look elsewhere if:
  • You need active maintenance or PHP 9.x+ support (this fork is PHP 8.4-only).
  • Your stack is non-Laravel/PHP (e.g., Node.js, Python).
  • You require advanced features like email parsing (use zbateson/mail-mime-parser) or IMAP (use ddeboer/imap).
• Consider only if:
  • You’re maintaining a legacy Laravel app tied to laminas/mail and cannot immediately migrate.
  • You need SMTP-specific tweaks (e.g., custom auth, server-specific quirks) not covered by Symfony Mailer’s abstractions.

How to Pitch It (Stakeholders)

For Executives: "This package lets us keep using laminas/mail with PHP 8.4—critical for our legacy [System X]—while avoiding a full rewrite to Symfony Mailer. It’s a low-risk stopgap to buy time for a future migration. The cost? Minimal: just a Composer dependency swap. The risk? None—it’s a direct fork with no new features, just compatibility. We’ll pair this with a 6-month migration plan to Symfony Mailer post-PHP 8.4."

For Engineering: *"oroinc/laminas-mail is a drop-in replacement for the abandoned laminas/mail package, adding PHP 8.4 support. Key perks:

• SMTP flexibility: Custom auth (PLAIN/LOGIN/CRAM-MD5), TLS/SSL, and server-specific fixes (e.g., Postfix reuse limits).
• Zero refactoring: Works with existing Laravel mailers/queues.
• Future-proof: We can migrate to Symfony Mailer incrementally. Tradeoff: No new development, but that’s fine—we’re just patching a compatibility gap. Let’s use it for [Project Y] and sunset it by [date]."*