- What does misaf/laravel-email-verification-emailable do?
- It is a Laravel package that adds Emailable as a deliverability driver for email validation. Instead of only checking syntax or DNS, it lets your application ask Emailable whether an address is deliverable, risky, or undeliverable through Laravel's validation flow. It plugs into the email verification driver system so you can switch providers through configuration.
- How do I install misaf/laravel-email-verification-emailable?
- Install it with composer require misaf/laravel-email-verification-emailable. Publish the package config if prompted and add your Emailable API key to .env. Then select the Emailable driver in your email verification configuration and run php artisan config:clear.
- How do I configure the Emailable API key in Laravel?
- Store your Emailable API key in .env, typically as EMAILABLE_API_KEY, and reference it from the package or email verification config file. Keep the key out of version control and use config caching in production. Check the README for the exact environment variable name the driver expects.
- Which Laravel versions does this package support, and is it still maintained?
- The package's composer.json lists its Laravel and PHP version constraints, so check that file or the README before installing. Also look at the GitHub repository for recent commits and tagged releases to judge maintenance. Because it is a thin driver around the Emailable API, the maintenance surface is small, but pin a version and review changes when you upgrade Laravel.
- How do I use Emailable as the email validation driver for my registration form?
- Set the email verification driver to Emailable in your config, then apply the validation rule to the email field on your registration or profile form. Keep Laravel's native email rule in the chain first so malformed input fails without an API call. Decide in your form request whether an undeliverable or risky result should block submission or only produce a warning.
- Does this package replace Laravel's built-in email validation?
- No. Laravel's email rule validates format, RFC compliance, and optionally DNS, while this package adds a deliverability lookup through Emailable on top of that. Keep the native rule and layer the Emailable check after it to avoid wasting API credits on obviously invalid strings.
- How can I test email validation without calling the Emailable API?
- Use Laravel's Http::fake() to return canned Emailable responses for deliverable, risky, and undeliverable addresses. Alternatively bind a fake driver or client in the container for feature tests. Assert how your validation rule and controller behave for each result, and never let the test suite hit the real Emailable API.
- What happens when the Emailable API is down or rate limited?
- Handle timeouts and non-200 responses explicitly in your validation flow, and decide whether to fail open or fail closed. Most consumer apps log the provider error and allow the address through rather than blocking signups during an outage. Add monitoring and consider caching successful results to reduce the chance of hitting rate limits.
- Should I cache Emailable verification results?
- Yes. Caching results by normalized email address cuts API cost and latency, and deliverability status usually does not change minute to minute. Store the result and a timestamp, then set a TTL that matches your risk tolerance. Re-check on sensitive actions like password resets or high-value signups if freshness matters.
- What are alternatives to using Emailable for Laravel email verification?
- Other deliverability providers have similar Laravel drivers, such as Kickbox, NeverBounce, and ZeroBounce, and the parent email verification package may support them. You can also stay with Laravel's native email and dns rules if you only need basic checks, or write a custom driver for another API. Compare accuracy, pricing, and rate limits before switching.