The email-validator package
- 'ghc-options: -O2' is rarely needed. Check that it is giving a real benefit and not just imposing longer compile times on your users.
Validate an email address using three techniques:
Ensuring that the length of local and domain parts is within the RFC-specified limits.
A syntax check using a regular expression, or the full RFC 5322 grammar (see the --rfc5322 option).
Confirmation of the existence of an MX record for the domain part of the address. This is not required; in fact many domains accept mail via an A record for e.g. example.com which is used in lieu of an MX record. This behavior can be controlled via the --accept-a flag.
These checks are performed in parallel using the number of available threads. To increase the number of threads, you can pass the appropriate flag to the GHC runtime.
This will set the number of threads to 25:
$ email-validator -i addresses.csv +RTS -N25
The input file (default: stdin) should be a list of email addresses, one per line. Empty lines will be ignored.
Valid email addresses will be written to the output file (default: stdout), one per line.
- No changelog available
|Versions||0.0.1, 0.0.2, 0.0.2|
|Dependencies||base (==4.*), bytestring (==0.10.*), cmdargs (==0.10.*), directory (==1.2.*), dns (==1.*), email-validate (==1.*), HUnit (==1.2.*), parallel-io (==0.3.*), pcre-light (>=0.4), test-framework (==0.8.*), test-framework-hunit (==0.3.*)|
|Maintainer||Michael Orlitzky <email@example.com>|
|Source repository||head: git clone http://michael.orlitzky.com/git/email-validator.git -b master|
|Upload date||Sat Oct 5 19:15:16 UTC 2013|
- email-validator-0.0.2.tar.gz [browse] (Cabal source package)
- Package description (included in the package)
For package maintainers and hackage trustees