Disposable emails can have very expensive negative effects in production databases (EDIT: Production servers ✌). Validating against them is definitely the best remedy and this has inspired my recent laravel package. A Laravel package providing validation rule against disposable email addresses.
Check it out here github.com/veeqtoh/laravel-active-email and feel free to suggest improvements and contributions,
Can you elaborate a little on how disposable or privacy-preserving email addresses negatively impact the database?
I understand the need for your package from a business perspective but not on a technical DB perspective.
Sure! But I think I poorly worded the statement. I meant more of a server impact than a database one.
Since most apps are built with the capacity to send emails (these could be welcome mails, account verification mails among others), emails sent to disposable addresses may bounce after the temporary email expires (in some cases, these emails are not even active in the first instance). High bounce rates can damage a domain's email deliverability, leading to legitimate emails being marked as spam.
Had this experience with one of our apps, requstory.com where the app's domain's reputation was affected due to high bounce rates. And so, I thought to write the package and make it highly customisable. Thanks for checking it out.
