Laravel Talario Laravel Package

Product Decisions This Supports

• Transactional email delivery for Laravel products: Supports common PM-owned flows such as password resets, receipts, account alerts, notifications, and customer communications through a Laravel-native Talario mail transport.
• Feature scope fit: v1.0.0 covers text and HTML messages, To/Cc/Bcc, Reply-To, regular attachments, and embedded images via embed()/embedData() with matching Content-IDs. This enables branded transactional emails, invoice attachments, support-routing via Reply-To, and Bcc-based archival/compliance workflows.
• Build vs buy: For teams already using or standardizing on Talario, this package reduces the need to build and maintain a custom HTTP mailer. The first stable release includes CI validation across supported Laravel/PHP combinations and live verification of HTML, attachment, Bcc, and embedded-image sends.
• Roadmap and platform planning: Supports Laravel 12 and 13, with PHP 8.2+ generally and PHP 8.3+ for Laravel 13. Product roadmaps targeting Laravel 13 must account for the PHP 8.3 minimum.
• Distribution decision: v1.0.0 is stable, but Packagist registration is pending. Until then, adoption requires adding the GitHub repository as a Composer VCS repository. This is an operational dependency, not a product blocker, but it should be tracked as an adoption gate.
• Reliability and duplicate-send policy: The package intentionally does not perform automatic HTTP retries, avoiding duplicate sends after ambiguous timeouts. Product should not promise transparent retry behavior. Any retry strategy must be designed at the application/queue layer with idempotency and monitoring.
• Security review support: HTTPS-only requests, disabled redirects, bounded timeouts, and sanitized transport exceptions provide useful defaults for security and compliance reviews.

When to Consider This Package

• Consider it when the application is on Laravel 12 or 13, meets the PHP version requirement, and Talario is the selected or planned email delivery provider.
• Consider it when the product needs standard transactional email capabilities: multipart text/HTML, Cc/Bcc, Reply-To, attachments, and embedded images.
• Consider it when the team accepts a temporary Composer VCS installation until Packagist registration, and can pin ^1.0 while tracking upstream releases.
• Consider it when no automatic retries is acceptable or desirable, especially for flows where duplicate sends after timeouts would be worse than a failed send requiring application-level recovery.
• Look elsewhere or delay adoption if dependency policy requires Packagist-only packages, if the application is on older Laravel/PHP versions, or if the team needs provider capabilities beyond this transport such as templates, webhooks, batch sending, scheduling, tags/metadata, inbound mail, or advanced observability—unless confirmed in the README/API limitations.
• Look elsewhere if the product requires built-in retry/failover, multi-provider abstraction, or a mature ecosystem with broad third-party support. Review the README’s documented API limitations before committing to a roadmap dependency.

How to Pitch It (Stakeholders)

• Executive summary: v1.0.0 is the first stable release of a Laravel mail transport for Talario. It reduces custom integration work for transactional email and supports common customer-communication features with security-conscious defaults. The main adoption caveats are that Packagist registration is pending and automatic retries are intentionally omitted.
• Engineering summary: The package offers Laravel package discovery, simple MAIL_MAILER=talario configuration, Laravel 12/13 support, text/HTML mail, Cc/Bcc, Reply-To, attachments, and embedded images. It has CI coverage across supported Laravel/PHP combinations and live send validation. Teams should pin the version, add the VCS repository until Packagist is available, and implement queueing/idempotency/monitoring rather than relying on transport retries.
• Product/operations summary: Use this package for standard transactional email on Laravel with Talario. Plan delivery monitoring and incident handling around ambiguous timeouts, and avoid promising automatic resend behavior. Bcc and Reply-To support can simplify compliance/archival and customer-support workflows. Track Packagist registration as the main distribution milestone before broad rollout.