email-validator: Perform basic syntax and deliverability checks on email addresses.
|Versions||0.0.1, 0.0.2, 0.0.3|
|Dependencies||base (==4.*), bytestring (==0.10.*), cmdargs (==0.10.*), directory (==1.2.*), dns (==1.*), email‑validate (==2.*), HUnit (==1.2.*), parallel‑io (==0.3.*), pcre‑light (>=0.4), tasty (==0.8.*), tasty‑hunit (==0.8.*) [details]|
|Maintainer||Michael Orlitzky <email@example.com>|
|Source repo||head: git clone http://michael.orlitzky.com/git/email-validator.git -b master|
|Uploaded||by MichaelOrlitzky at Sat Mar 15 19:17:51 UTC 2014|
|Downloads||1216 total (11 in the last 30 days)|
|Rating||(no votes yet) [estimated by rule of succession]|
|Status||Docs not available [build log]
Last success reported on 2015-05-19 [all 7 reports]
Hackage Matrix CI
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
Confirmation of the existence of an
MXrecord for the domain part of the address. This is not required; in fact many domains accept mail via an
Arecord for e.g. example.com which is used in lieu of an
MXrecord. This behavior can be controlled via the
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
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.
For package maintainers and hackage trustees