This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author r.david.murray
Recipients barry, eric.smith, jpic, r.david.murray
Date 2019-07-13.21:37:54
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1563053875.33.0.578442731401.issue37492@roundup.psfhosted.org>
In-reply-to
Content
Right, those absolutely are valid addresses.  A resolver will normally look up a name with an internal dot first as if it were an FQDN, but if it does so and does not get an answer it will then look it up again as a "local" address (appending in turn the strings from the 'search' directive in resolv.conf or equivalent) *if* it does not end in a final dot.  If it does end in a final dot, no further lookup as local is done.

While it isn't *normal* to send email to a TLD using a trailing dot, it is *legal*.  In theory the address 'postmaster@com.' ought to be a valid email address (I doubt that it actually is, though). On the other hand, I will be very surprised if *all other* TLDs are without valid email addresses, especially the new ones.  It is also easy to imagine an environment using email with private single label domain names using trailing dots specifically to suppress appending of search domains for sandboxing reasons.  Thus the email library must support it as valid, both for RFC reasons and for practical reasons.
History
Date User Action Args
2019-07-13 21:37:55r.david.murraysetrecipients: + r.david.murray, barry, eric.smith, jpic
2019-07-13 21:37:55r.david.murraysetmessageid: <1563053875.33.0.578442731401.issue37492@roundup.psfhosted.org>
2019-07-13 21:37:55r.david.murraylinkissue37492 messages
2019-07-13 21:37:55r.david.murraycreate