- What is dniccum/custom-email-sender and what does it do?
- It is a Laravel Nova tool that adds an admin panel screen for sending custom email messages using your application's existing mail configuration and transport credentials. It registers through NovaServiceProvider::tools(), ships PHP controllers that call Laravel's Mail facade, and includes a Vue front end. It is not a standalone mailer and not a marketing or CRM broadcast system; it is a narrow operator tool for ad-hoc transactional or announcement mail.
- Which Laravel, PHP, and Nova versions does dniccum/custom-email-sender support?
- The last release was December 2020, so expect composer constraints around PHP 7.2 to 8.0, Laravel 6 to 8, and Nova 3. The packaged tool assets use a Vue 2 pipeline, which will not load in Nova 4 or 5. Always check the composer.json constraints against your host application before committing to an install.
- How do I install dniccum/custom-email-sender in a Laravel Nova app?
- Run composer require dniccum/custom-email-sender, publish the config and assets, register the tool in NovaServiceProvider::tools(), and run nova:publish. Install into staging first and verify tool registration and asset publishing work as expected. Then validate sends against each mail transport you actually use, such as SMTP, SES, Postmark, or Mailgun.
- Can I use dniccum/custom-email-sender outside of Laravel Nova?
- No. It is a Nova Tool rather than a general Laravel package, and it only registers through NovaServiceProvider::tools() on Nova 3. If your application is not a Nova shop, the package is a non-starter. The underlying pattern of a Mailable, a Blade view, and an admin action is roughly a one-day internal build if you want the same feature.
- Does dniccum/custom-email-sender work with Laravel 10, Laravel 11, or Nova 4 and 5?
- Almost certainly not as a drop-in. Nova 4 and later moved to Vue 3 and Inertia, and this package's Vue 2 tool components will not load there. With zero reverse dependencies and only 62 stars, there is no community evidence of compatibility with modern stacks, so you would be the first to find out. Treat it as a reference implementation to fork rather than a dependency to install.
- How does the package override the mail sender per message?
- It lets a trusted operator specify a custom from address, from name, or SMTP configuration for an individual message instead of editing config/mail.php globally. Sends go through Laravel's Mail facade against the host application's existing transport settings, so global mail configuration stays untouched. Confirm in the source whether it composes Mailables or uses raw Mail::send with inline HTML, since that affects templating and testability.
- Is it safe to let admins send arbitrary email from the Nova panel?
- It is a real abuse vector: spam relay, phishing from your own domain, and HTML or attachment injection are all plausible risks. Confirm the tool enforces Nova authorization gates or policies and per-user permissions before exposing it to any operator. Add a send-log or audit table and, ideally, recipient allow-listing, because the assessment flags these as open questions rather than shipped guarantees.
- Are emails sent synchronously or queued by dniccum/custom-email-sender?
- The documentation does not make this clear, but the risk is that inline sends block the request and time out on large recipient lists. If you adopt the package, wrap the send in a queued job and add batching and rate limiting yourself. This is one of the main reasons a fork-and-own approach often has a better total cost of ownership.
- Is dniccum/custom-email-sender still maintained?
- There has been no release in over four years, it has a single maintainer, zero reverse dependencies, and only 62 stars. Treat it as unmaintained and plan on owning the code if you adopt it. Its package health score reflects a well-formed small package rather than an actively maintained one.
- What are the alternatives if dniccum/custom-email-sender is abandoned or incompatible?
- If you are on Nova 4 or 5, or Laravel 10 and 11, fork the tool's controllers, mailables, and Vue components into your app and update the front end to current Nova conventions. Or build it directly: a Mailable, a Blade view, a Nova action, and a send-log table give you the same capability with a known blast radius. For bulk or marketing mail, use a dedicated email service provider or an ESP-backed broadcast service instead of an ad-hoc admin sender.