- How do I install and set up mydnic/laravel-subscribers?
- Install it with Composer using composer require mydnic/laravel-subscribers, then publish the config and migrations with the vendor:publish Artisan command and run php artisan migrate. Setup also involves configuring a Mailgun, SES, or Postmark transport plus a running queue worker and scheduler, since campaign sending and tracking sit on Laravel's standard primitives. Review the published config for table names and route prefixes before migrating, and confirm the service provider is auto-discovered on your Laravel version.
- Does mydnic/laravel-subscribers support double opt-in and unsubscribe links?
- The package is built around subscription capture, opt-in, and unsubscribe flows, so confirmation and unsubscribe handling are part of its intended scope. Because compliance details are easy to assume, verify in the source that confirmation tokens expire and are single-use, and that opt-in source, timestamp, and IP are recorded for audit. Also check that unsubscribe supports Gmail and Yahoo bulk sender one-click requirements, including the List-Unsubscribe header.
- Which Laravel and PHP versions does laravel-subscribers support?
- It targets modern Laravel applications, with Laravel 10 and 11 being the realistic fit for teams already running a queue worker and scheduler. There is no strong evidence of a published CI matrix covering multiple PHP and Laravel combinations, so check composer.json constraints and the actual tag history before committing. On older Laravel versions, expect to fork or pin rather than rely on upstream support.
- Does laravel-subscribers send campaigns itself, or do I still need an ESP?
- It sends through Laravel's mailer, so you still configure a transport such as Mailgun, SES, Postmark, or SMTP. The package supplies the subscriber model, campaign structures, and tracking layer rather than deliverability infrastructure. Sender reputation, domain warm-up, and bounce handling remain your responsibility unless the source shows otherwise.
- Is campaign sending queued, and can I throttle it to respect provider rate limits?
- Sending is expected to run through Laravel queued jobs and the scheduler rather than a synchronous loop, which is the only practical approach for a real mailing list. Whether the package ships batching and rate limiting out of the box must be confirmed in the source, since provider rate limits are the usual failure point on large lists. Many teams add a rate-limited queue connection or custom middleware to cap throughput.
- How does open and click tracking work, and are the tracking routes secure?
- Tracking typically works through a pixel and a redirect endpoint that log opens and clicks into package tables, which means your application exposes public routes. Confirm those URLs are signed or tokenized and whether tracking can be disabled per environment, since unsigned tracking endpoints are a common source of abuse. Check that the routes coexist with your existing middleware, CSP, and any API gateway in front of the app.
- Can I use it alongside my existing users table?
- The package assumes the host app owns users, auth, and routing, and it can work with a separate subscribers table or a mapping to your users. Treat subscribers as distinct from users, because conflating them creates privacy, deletion, and consent headaches later. Plan a pivot or mapping layer and decide early how account deletions and merges propagate to subscription records.
- Does it handle bounces, complaints, and suppression lists?
- Answer this before going live: confirm whether the package ingests provider webhooks for bounces and complaints or whether the host application must. Suppression lists are often the difference between a temporary deliverability dip and a burned sending domain. If the package does not cover it, budget a small custom webhook handler that flags subscribers and blocks future sends.
- Is laravel-subscribers GDPR and CAN-SPAM compliant out of the box?
- Compliance is a property of your implementation, not the package: consent records, double opt-in, audit trails, and one-click unsubscribe all need verification in code. GDPR also requires a deletion path for subscriber PII, so check whether the package migrations cascade or need custom cleanup. Do not assume compliance from the description; audit the migrations and controllers yourself.
- Is laravel-subscribers actively maintained, and what should I watch out for?
- It is an early-stage, single-maintainer package with modest adoption (around 26 GitHub stars at evaluation time), so treat it as a scoped dependency rather than a load-bearing revenue path. The MIT license means you can fork if upstream stalls, but that does not solve ongoing security patching. Check issue and PR responsiveness over the last six months, confirm the real tag history, and watch for open advisories. If you need heavy segmentation, automation, or multi-tenant sending, a mature ESP or a package like Mailcoach is a better fit.