- What does misaf/laravel-email-verification-bouncer do?
- It is the bouncer driver package for the Laravel Email Verification package by misaf. It validates email addresses during signup and helps block disposable, role-based, and bouncing addresses so your user list stays cleaner. It is aimed at reducing failed deliveries and risky registrations in Laravel applications.
- How do I install misaf/laravel-email-verification-bouncer with Composer?
- Install it with Composer using composer require misaf/laravel-email-verification-bouncer. Because it is a subtree split of the main misaf/laravel-email-verification package, you will usually install and configure that parent package rather than working with this repository directly. Check the parent package README for the recommended setup steps.
- Is this package standalone or a subtree split of another Laravel package?
- This repository is a read-only subtree split of the Laravel Email Verification Drivers from misaf/laravel-email-verification. That means you should not send pull requests or open issues here. Contribute changes and report bugs in the main misaf/laravel-email-verification repository instead.
- What kinds of risky email addresses can it block?
- The package is designed to detect disposable email domains, role-based addresses such as admin@ or support@, and addresses that are likely to bounce. These checks help prevent signups that could hurt deliverability or fill your user table with low-quality accounts. The exact detection drivers depend on the parent package's configuration.
- How do I configure email verification rules in Laravel?
- Configuration comes from the parent misaf/laravel-email-verification package, so publish and edit its config file rather than expecting separate settings in this split repository. The parent README is the source of truth for available drivers and rule options. Keep your config in version control so email validation behavior is consistent across environments.
- Which Laravel versions does this package support?
- The package follows the Laravel Email Verification package's Composer constraints, so supported Laravel versions are defined in its composer.json. Check those constraints on Packagist before adding it to an older Laravel project. If you need a specific Laravel release, verify compatibility in the parent package's documentation or test suite.
- Can I use it in a Laravel registration form validation rule?
- You can use the package's email verification rules as part of your Laravel registration validation flow, typically alongside Laravel's built-in email rule. It is intended to reject risky signups before the account is created. Confirm the exact rule class or driver name in the parent package documentation.
- Does it call an external API to detect bouncing emails?
- The package overview does not specify a single required external service; detection may depend on the driver you enable in the parent package. Some email verification approaches rely on DNS or third-party lookups, so review the parent package's driver documentation and any API key requirements. Avoid assuming it is fully offline until you confirm the driver behavior.
- How do I test disposable or role-based email blocking in my Laravel app?
- In tests, fake or bind the verification driver so your test suite does not depend on live DNS or third-party email checks. Then assert that disposable and role-based addresses fail validation while normal addresses pass. Use Laravel's validation testing helpers and keep separate tests for each rule or driver you enable.
- Is it production-ready for high-volume Laravel signups?
- For production, treat email verification as one layer of signup protection and monitor bounce rates and false positives after rollout. Cache or batch any slow external checks so high-volume registration endpoints stay responsive. Because this is a subtree split, review the parent package's release history and maintenance activity before relying on it long term.