Weave Code
Laravel Mail Scheduler Laravel Package
oneduo/laravel-mail-scheduler
Schedule outgoing Laravel mail with a simple, database-backed approach: store messages with send times, dispatch them via Laravel’s scheduler and queue, and manage pending deliveries through an easy Eloquent API. Useful for reminders, digests, and delayed notifications.
An efficient way to send emails in batches from your Laravel application
Frequently asked questions about Laravel Mail Scheduler
- What is oneduo/laravel-mail-scheduler used for in Laravel?
- It is an additive Laravel package for scheduling outgoing mailables in a database-backed way. You store messages with send times, dispatch them through Laravel's scheduler and queue, and manage pending deliveries through an Eloquent API. It is useful for reminders, digests, delayed notifications, and other deferred sends that need durable lifecycle state.
- How do I install and configure oneduo/laravel-mail-scheduler?
- The integration surface is small: install via Composer, publish the config and migrations, register the scheduled command, and connect its dispatch cadence to schedule:run. It fits applications already using a relational database, the Laravel scheduler, and a queue-backed mail pipeline. Confirm the exact command and config names from the package release notes before rolling it out.
- Does oneduo/laravel-mail-scheduler support Laravel 11?
- Yes, the v1.0.0 headline is Laravel 11 support, and that is the key compatibility item for teams planning an L11 upgrade. The provided evaluation does not confirm whether older Laravel versions were dropped, so verify the support matrix in the repository. Treat the move from 0.2.0 to 1.0.0 as a compatibility review rather than a routine patch.
- Which Laravel and PHP versions are supported in v1.0.0?
- The context explicitly calls out Laravel 11 support for v1.0.0, but it does not state the exact PHP minimum or whether Laravel 8, 9, or 10 remain supported. Check the package composer.json, release notes, and CI matrix for the authoritative support matrix. For an L11 upgrade, validate PHP 8.2 or 8.3, Laravel 11, your database driver, and your queue driver together.
- Is oneduo/laravel-mail-scheduler a replacement for Laravel's queue or Mail::later()?
- No. It does not replace Laravel's mailer or queue; it adds durable scheduling and lifecycle state on top of them. It is most valuable when you need cancellable, auditable, database-backed deferred sends beyond simple queue delays. If a basic queue delay is sufficient, the package is optional and adds a persistence layer you must operate.
- How does laravel-mail-scheduler prevent duplicate emails with multiple scheduler runners?
- The provided evaluation flags duplicate-send prevention under multiple scheduler runners as a key question, but it does not confirm whether the dispatch command uses locking or batching. Review the command implementation and test your scheduler topology before relying on it at scale. Until that behavior is confirmed, avoid overlapping schedule:run runners or add external coordination.
- What changed from 0.2.0 to 1.0.0 in oneduo/laravel-mail-scheduler?
- The release notes are described as sparse for a major version bump, with Laravel 11 support as the headline. No explicit breaking changes are listed, but moving from 0.2.0 to 1.0.0 commonly implies a changed compatibility baseline and may include schema, migration, config, or command-behavior changes. Diff the published config and migrations and test existing scheduled records before upgrading.
- Can I upgrade to Laravel 11 with laravel-mail-scheduler 1.0.0?
- The v1.0.0 release is positioned to support Laravel 11 and may unblock an L11 upgrade. Sequence the package bump with the framework upgrade rather than after it, and validate migrations, scheduler behavior, queue dispatch, and mail transport in staging. Keep a documented rollback path to 0.2.0 plus the prior framework version.
- Is oneduo/laravel-mail-scheduler production-ready and well maintained?
- The 1.0.0 designation is a positive signal for API stability, but it is not evidence of production hardening. The evaluation notes a small team, a first-time contributor, and sparse release notes, so the main risks are undocumented changes and long-term maintenance or bus factor. Review CI and test coverage, pin dependencies, and maintain a rollback plan.
- When should I use database-backed scheduled mail instead of simple queue delays?
- Use it when you need durable, cancellable, auditable deferred sends such as reminders, digests, and delayed notifications. It is best suited to conventional Laravel applications with a relational database, reliable scheduler or cron, and a queue-backed mail pipeline. Avoid it for non-Laravel services or environments without a reliable scheduler, and skip it when simple queue delay is enough.
Weaver
How can I help you explore Laravel packages today?