doc,email-validator: document the new NULLMX handling

diff --git a/doc/man1/email-validator.1 b/doc/man1/email-validator.1
index 1e0e144940db48e78f3b7ddc5428457c81d7b86b..605b57010256b19858024cf973232358b757a6f3 100644 (file)
--- a/doc/man1/email-validator.1
+++ b/doc/man1/email-validator.1
@@ -33,10 +33,12 @@ grammar (see the \fB\-\-rfc5322\fR option).
 
 .IP \[bu]
 Confirmation of the existence of an \fIMX\fR record for the domain
-part of the address. This is not required; in fact many domains accept
-mail via an \fIA\fR record for e.g. example.com which is used in lieu
-of an \fIMX\fR record. This behavior can be controlled via the
-\fR\-\-accept\-a\fR flag.
+part of the address. NULLMX (RFC7505) records are not accepted. This
+is not required; in fact many domains accept mail via an \fIA\fR
+record for (say) example.com which is used in lieu of an \fIMX\fR
+record. This behavior can be controlled via the \fR\-\-accept\-a\fR
+flag, but note that \fR\-\-accept\-a\fR is ignored for domains that
+have NULLMX records.
 
 .P
 These checks are performed in parallel using the number of available

diff --git a/email-validator.cabal b/email-validator.cabal
index 6627128b23fd5e7a16422d88872275cc8bd4eaea..3e975f393b92cdbfefb234883f2640d4cf97de25 100644 (file)
--- a/email-validator.cabal
+++ b/email-validator.cabal
@@ -23,10 +23,13 @@ description:
     * 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.
+    * Confirmation of the existence of an @MX@ record for the domain
+      part of the address. NULLMX (RFC7505) records are not
+      accepted. This is not required; in fact many domains accept mail
+      via an @A@ record for (say) example.com which is used in lieu of
+      an @MX@ record. This behavior can be controlled via the
+      @--accept-a@ flag, but note that @--accept-a@ is ignored for
+      domains that have NULLMX records.
 
   These checks are performed in parallel using the number of available
   threads. To increase the number of threads, you can pass the