Weave Code
Mail Storage Bundle Laravel Package
nuxia/mail-storage-bundle
A Symfony bundle for persisting outgoing emails so they can be inspected, audited, and debugged later. Integrates with the mailer to capture messages and store them through configurable storage with simple setup and service configuration.
Bundle to store your sent mail
Frequently asked questions about Mail Storage Bundle
- Can I use nuxia/mail-storage-bundle in a Laravel application?
- No. It is a Symfony bundle built around Symfony Mailer events, dependency injection bundle extension semantics, and likely Doctrine ORM, none of which map onto Laravel's Mail facade, MessageSent event, or Eloquent. Composer will install it, but there is no bundle auto-registration path or listener wiring that Laravel understands, so you get no working feature. Treat it as a design reference rather than a dependency.
- Is nuxia/mail-storage-bundle a Laravel package or a Symfony bundle?
- It is a Symfony bundle, despite being evaluated alongside Laravel packages. The Bundle suffix, the Nuxia vendor, a Symfony and PHP consultancy, and the Composer namespace all follow Symfony's bundle model. Its listener subscribes to Symfony Mailer events and is wired through Symfony's event dispatcher contract, so it will not run against Laravel's mailer without a rewrite.
- How do I install nuxia/mail-storage-bundle?
- You would run composer require nuxia/mail-storage-bundle and then register the bundle in a Symfony kernel's bundles.php, which is the standard Symfony path. In Laravel there is no equivalent registration step, so installation alone does not produce a functioning feature. Before installing anywhere, read the composer.json constraints for PHP, symfony/*, and Doctrine requirements.
- Which Laravel versions does nuxia/mail-storage-bundle support?
- None. The package targets Symfony, so it makes no claim of Laravel 8, 9, 10, or 11 support. Laravel 10 and 11 pull Symfony 6 and 7 components, so a bundle pinned to Symfony 4 or 5 era constraints will either fail dependency resolution or force downgrades elsewhere in your tree. Verify with a throwaway branch before spending estimation time.
- What is the best Laravel alternative to nuxia/mail-storage-bundle?
- Build it in-house. A queued listener on Illuminate\Mail\Events\MessageSent that writes to a dedicated Eloquent model is roughly a day of work and gives you full control over schema, retention, and PII handling. That approach avoids the version skew and abandonment risk of a single-vendor Symfony bundle with zero dependents.
- How do I store sent emails in Laravel?
- Listen for Illuminate\Mail\Events\MessageSent, which fires after the mailer sends a message, and persist the message plus the envelope recipients. Queue the listener so persistence never blocks delivery, and write to a dedicated table with explicit retention and encryption rules. Define the fields you need first: recipients, subject, body, headers, attachments, message ID, and status.
- Does nuxia/mail-storage-bundle store email bodies and attachments?
- The available metadata does not document the storage backend, so whether it captures full MIME bodies and attachments is unknown. That matters because full-body and attachment storage drives database growth, PII exposure, and encryption obligations. Confirm this in the source before treating it as an audit trail or compliance record.
- Is nuxia/mail-storage-bundle actively maintained?
- There is no observable signal that it is. It has zero stars, zero dependents, and a zero score, so no downstream production usage is visible, and there is no documented release cadence or security-response process. Assume single-vendor maintenance and plan accordingly before relying on it.
- Can I migrate from nuxia/mail-storage-bundle to a Laravel solution?
- There is nothing to migrate. With no existing integration, dependents, or stored data, the move is a design exercise rather than a data migration. Define your persistence contract first, then build the MessageSent listener, since the zero switching cost works in your favor.
- What should I check before adopting nuxia/mail-storage-bundle?
- Confirm your target stack first, since the answer changes this from no to maybe. Then read composer.json for PHP, symfony/*, and Doctrine constraints, identify the storage backend and whether bodies and attachments are captured, and check for a named maintainer with commits in the last 12 months. Finally, pin down the business requirement: audit trail, resend capability, compliance retention, or deliverability debugging.
Weaver
How can I help you explore Laravel packages today?