You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
`check_deliverability=True`: Set to `False` to skip the domain name MX DNS record check.
144
+
`check_deliverability=True`: Set to `False` to skip the domain name DNS record checks.
142
145
143
146
`allow_empty_local=False`: Set to `True` to allow an empty local part (i.e.
144
147
`@example.com`), e.g. for validating Postfix aliases.
@@ -323,9 +326,7 @@ ValidatedEmail(
323
326
ascii_email='test@joshdata.me',
324
327
ascii_local_part='test',
325
328
ascii_domain='joshdata.me',
326
-
smtputf8=False,
327
-
mx=[(10, 'box.occams.info')],
328
-
mx_fallback_type=None)
329
+
smtputf8=False)
329
330
```
330
331
331
332
For the fictitious address `example@ツ.life`, which has an
@@ -392,6 +393,7 @@ are:
392
393
|`smtputf8`| A boolean indicating that the [SMTPUTF8](https://tools.ietf.org/html/rfc6531) feature of your mail relay will be required to transmit messages to this address because the local part of the address has non-ASCII characters (the local part cannot be IDNA-encoded). If `allow_smtputf8=False` is passed as an argument, this flag will always be false because an exception is raised if it would have been true. |
393
394
|`mx`| A list of (priority, domain) tuples of MX records specified in the DNS for the domain (see [RFC 5321 section 5](https://tools.ietf.org/html/rfc5321#section-5)). May be `None` if the deliverability check could not be completed because of a temporary issue like a timeout. |
394
395
|`mx_fallback_type`|`None` if an `MX` record is found. If no MX records are actually specified in DNS and instead are inferred, through an obsolete mechanism, from A or AAAA records, the value is the type of DNS record used instead (`A` or `AAAA`). May be `None` if the deliverability check could not be completed because of a temporary issue like a timeout. |
396
+
|`spf`| Any SPF record found while checking deliverability. |
395
397
396
398
Assumptions
397
399
-----------
@@ -401,10 +403,12 @@ strictly conform to the standards. Many email address forms are obsolete
401
403
or likely to cause trouble:
402
404
403
405
* The validator assumes the email address is intended to be
404
-
deliverable on the public Internet. The domain part
405
-
of the email address must be a resolvable domain name.
406
-
[Special Use Domain Names](https://www.iana.org/assignments/special-use-domain-names/special-use-domain-names.xhtml)
407
-
and their subdomains are always considered invalid (except see
406
+
usable on the public Internet. The domain part
407
+
of the email address must be a resolvable domain name
408
+
(without NULL MX or SPF -all DNS records) if deliverability
409
+
checks are turned on.
410
+
Most [Special Use Domain Names](https://www.iana.org/assignments/special-use-domain-names/special-use-domain-names.xhtml)
411
+
and their subdomains are considered invalid (except see
408
412
the `test_environment` parameter above).
409
413
* The "quoted string" form of the local part of the email address (RFC
410
414
5321 4.1.2) is not permitted --- no one uses this anymore anyway.
0 commit comments