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 eric.smith
Recipients barry, eric.smith, jpic, r.david.murray
Date 2019-07-03.11:09:42
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1562152182.93.0.459385815944.issue37492@roundup.psfhosted.org>
In-reply-to
Content
Counterpoint: I just sent an email to "info@info.", and Thunderbird and my MTA (postfix) and my mail relay all accepted it. I guess it's possible that a TLD (especially one of the newer ones) could accept email addresses in the TLD itself.

It turns out that "info@info." isn't a mailbox as of right now, but I think it's a valid and accepted address, at least by the software listed above. And it could be a valid mailbox, just isn't in this particular case.

Maybe the more conservative approach is to say that "info@info." (and "a@b.", etc.) should be considered valid email addresses.

If you were actually trying to send email to a mailbox in the "info" TLD, I think most resolvers would resolve "info" as a relative domain name, which isn't what we'd want to happen: you'd have to specify the domain as "info.".
History
Date User Action Args
2019-07-03 11:09:42eric.smithsetrecipients: + eric.smith, barry, r.david.murray, jpic
2019-07-03 11:09:42eric.smithsetmessageid: <1562152182.93.0.459385815944.issue37492@roundup.psfhosted.org>
2019-07-03 11:09:42eric.smithlinkissue37492 messages
2019-07-03 11:09:42eric.smithcreate