Download the PHP package pross/disposable-email-domains without Composer
On this page you can find all versions of the php package pross/disposable-email-domains. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download pross/disposable-email-domains
More information about pross/disposable-email-domains
Files in pross/disposable-email-domains
Package disposable-email-domains
Short Description This repo contains a list of disposable and temporary email address domains often used to register dummy users in order to spam/abuse some services.
License
Informations about the package disposable-email-domains
List of disposable email domains
This repo contains a list of disposable and temporary email address domains often used to register dummy users in order to spam/abuse some services.
Originally collected to filter new user registration at https://usegalaxy.org and later merged with other lists found online. I cannot guarantee all of these can still be considered disposable but they probably were at one point in time.
Whitelist
The file whitelist.conf gathers email domains that are often identified as disposable but in fact are not.
Example Usage
Python
Available as PyPI module thanks to @di
PHP contributed by @txt3rob and @deguif
Ruby on Rails contributed by @MitsunChieh
In resource model, usually it is user.rb
Contributing
Feel free to create PR with additions or request removal of some domain (with reasons).
Use
$ cat disposable_email_blacklist.conf your_file | tr '[:upper:]' '[:lower:]' | sort -f | uniq -i > new_file.conf
$ comm -23 new_file.conf whitelist.conf > disposable_email_blacklist.conf
to add contents of another file in the same format (only second level domains on new line without @). It also converts uppercase to lowercase, sorts, removes duplicates and removes whitelisted domains.
Changelog
-
12/6/16 - Available as PyPI module thanks to @di
- 7/27/16 - Converted all domains to the second level. This means that starting from this commit the implementers should take care of matching the second level domain names properly i.e.
@xxx.yyy.zzz
should matchyyy.zzz
in blacklist more info in #46