email-validator: Perform basic syntax and deliverability checks on email addresses.
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 +RTS -N25 < addresses.csv
input (via stdin) should be a list of email addresses,
one per line. Empty lines will be ignored.
Valid email addresses will be written to stdout, one per line.
|Versions [RSS] [faq]||0.0.1, 0.0.2, 0.0.3, 1.0.0|
|Dependencies||base (>=4.9 && <5), bytestring (>=0.10), cmdargs (>=0.10), dns (>=2), 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>|
|Revised||Revision 1 made by HerbertValerioRiedel at 2019-03-17T15:33:27Z|
|Source repo||head: git clone http://gitweb.michael.orlitzky.com/email-validator.git -b master|
|Uploaded||by MichaelOrlitzky at 2019-03-17T14:34:14Z|
|Downloads||2880 total (24 in the last 30 days)|
|Rating||(no votes yet) [estimated by Bayesian average]|
Docs not available [build log]
Last success reported on 2019-03-17 [all 3 reports]
- email-validator-1.0.0.tar.gz [browse] (Cabal source package)
- Package description (revised from the package)
Note: This package has metadata revisions in the cabal description newer than included in the tarball. To unpack the package including the revisions, use 'cabal get'.