4 author: Michael Orlitzky
5 maintainer: Michael Orlitzky <michael@orlitzky.com>
8 license-file: doc/LICENSE
11 doc/man1/email-validator.1
13 Perform basic syntax and deliverability checks on email addresses.
15 Validate an email address using three techniques:
17 * Ensuring that the length of local and domain parts is within the
20 * A syntax check using a regular expression, or the full RFC 5322
21 grammar (see the @--rfc5322@ option).
23 * Confirmation of the existence of an @MX@ record for the domain part of
24 the address. This is not required; in fact many domains accept mail
25 via an @A@ record for e.g. example.com which is used in lieu of an @MX@
26 record. This behavior can be controlled via the @--accept-a@ flag.
28 These checks are performed in parallel using the number of available
29 threads. To increase the number of threads, you can pass the
30 appropriate flag to the GHC runtime.
32 This will set the number of threads to 25:
35 $ email-validator -i addresses.csv +RTS -N25
40 The @input@ file (default: stdin) should be a list of email addresses,
41 one per line. Empty lines will be ignored.
45 Valid email addresses will be written to the output file (default:
46 stdout), one per line.
49 executable email-validator
56 email-validate == 1.*,
60 test-framework == 0.8.*,
61 test-framework-hunit == 0.3.*
77 -fwarn-missing-signatures
82 -fwarn-incomplete-record-updates
83 -fwarn-monomorphism-restriction
98 type: exitcode-stdio-1.0
99 hs-source-dirs: src test
100 main-is: TestSuite.hs
103 bytestring == 0.10.*,
107 email-validate == 1.*,
109 parallel-io == 0.3.*,
111 test-framework == 0.8.*,
112 test-framework-hunit == 0.3.*
114 -- It's not entirely clear to me why I have to reproduce all of this.
118 -fwarn-missing-signatures
119 -fwarn-name-shadowing
123 -fwarn-incomplete-record-updates
124 -fwarn-monomorphism-restriction
125 -fwarn-unused-do-bind
132 source-repository head
134 location: http://michael.orlitzky.com/git/email-validator.git