Skip to content
This repository has been archived by the owner on Oct 2, 2024. It is now read-only.

Test unicode emails #18

Closed
wants to merge 1 commit into from
Closed

Conversation

KyleAMathews
Copy link
Contributor

for #17

@@ -11,6 +11,9 @@
["test@nominet.org.uk", "valid"],
["test@about.museum", "valid"],
["a@iana.org", "valid"],
["êjness@iana.com", "valid"],
["ñoñó1234@iana.com", "valid"],
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@skeggse even with unicode character support, this fails on the DNS lookup because of iana.com vs iana.org.

@@ -11,6 +11,9 @@
["test@nominet.org.uk", "valid"],
["test@about.museum", "valid"],
["a@iana.org", "valid"],
["êjness@iana.com", "valid"],
["ñoñó1234@iana.com", "valid"],
["伊昭傑@郵件.商務", "valid"],
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@skeggse same DNS issue here. The MX resolution fails for 郵件.商務

Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hm, gotcha.

This is a good problem to notice. This also indicates that unicode support in the domain names will break checkDNS, as the resolve family of functions are not unicode compatible or aware, which goes back to my question about punycode. It seems we'll need just a little more to avoid breaking existing functionality in unexpected ways.

@WesTyler WesTyler mentioned this pull request Feb 6, 2017
@skeggse
Copy link
Owner

skeggse commented Jun 22, 2017

11253ee

@skeggse skeggse closed this Jun 22, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants