Laravel Snip Laravel Package

Product Decisions This Supports

• Local/staging mail safety: Adopt SNIP_MAIL_CATCH=true as the standard dev/staging mail interception mechanism to prevent accidental customer emails, especially in apps that select mailers per message (Mail::mailer('shop_sk')) rather than relying only on the default mailer.
• Build vs. buy: This package is a low-cost, Laravel-native alternative to external SMTP catchers for local development. It is not a replacement for production ESPs, deliverability tooling, or cross-framework mail-testing services.
• QA and support workflows: The playground Mail tab inbox—with a queue-worker simulation button—gives QA and support a fast way to inspect caught mail, including queued mail, without configuring an external inbox.
• Roadmap and environment standardization: Standardize dev/staging .env conventions around SNIP_MAIL_CATCH=true; add onboarding guidance to restart queue workers after enabling it.
• Release management: v0.3.6 is additive, with no apparent breaking changes. Teams must re-publish assets (php artisan vendor:publish --tag=snip-assets --force) to see the updated Mail tab guidance and inbox UI.

When to Consider This Package

Consider adoption when:

• The application is Laravel/PHP and needs a simple way to catch mail in local or non-production environments.
• The app uses multiple mailers or per-mail mailer selection; the new SNIP_MAIL_CATCH=true flag is specifically relevant because MAIL_MAILER=snip only covered the default mailer.
• Queued mail is part of the workflow; the release explicitly addresses queue-worker behavior and reminds teams to restart workers.
• Teams want an in-app playground inbox instead of, or alongside, external tools like Mailtrap or Mailhog.
• You want a lightweight, package-level solution rather than building and maintaining custom mail-interception logic.

Look elsewhere when:

• You need production-grade email delivery, deliverability analytics, or compliance controls.
• You need cross-language or non-Laravel support.
• You require advanced mail assertion/testing APIs beyond local inspection.
• Your organization mandates cloud-based shared inboxes or vendor-managed email testing infrastructure.

How to Pitch It (Stakeholders)

For executives: This release closes a meaningful safety gap in non-production environments. Previously, apps that chose a mailer per message could still send real email from dev or staging; SNIP_MAIL_CATCH=true catches every mail regardless of mailer. That reduces the risk of accidentally emailing customers and speeds up QA. It is an additive, low-risk update with no apparent breaking changes, though assets must be re-published.

For engineering: v0.3.6 makes mail catching reliable across all mailers, not just the default. The playground Mail tab now shows an inbox and can simulate a queue worker catching mail, which helps validate queued-mail behavior. Update the recommended setup to use SNIP_MAIL_CATCH=true, remind teams to restart queue workers after enabling it, and re-publish assets with php artisan vendor:publish --tag=snip-assets --force.