3 ms·
This article is clearly invalid because attempting to email Z̴̧̡̢̨̛A̷̡̡̢̢̡L̶̢̧̢̪̬Ģ̵̡̢̢̧̛Ơ̵̡̡̬͇̬ ̵̡̧̢̛̳Ċ̷̢̨̢̼̰Ǫ̷̨̧̢̛͎M̵̡̨̖̹̣E̴̢̧̨̨̛S̸̱̠̹̮̣@gmail.com using Gmail
by lucasgonze 6y ago
This article is clearly invalid because attempting to email Z̴̧̡̢̨̛A̷̡̡̢̢̡L̶̢̧̢̪̬Ģ̵̡̢̢̧̛Ơ̵̡̡̬͇̬ ̵̡̧̢̛̳Ċ̷̢̨̢̼̰Ǫ̷̨̧̢̛͎M̵̡̨̖̹̣E̴̢̧̨̨̛S̸̱̠̹̮̣@gmail.com using Gmail produces this error:
Error
The address "Z̴̧̡̢̨̛A̷̡̡̢̢̡L̶̢̧̢̪̬Ģ̵̡̢̢̧̛Ơ̵̡̡̬͇̬ ̵̡̧̢̛̳Ċ̷̢̨̢̼̰Ǫ̷̨̧̢̛͎M̵̡̨̖̹̣E̴̢̧̨̨̛S̸̱̠̹̮̣@gmail.com" in the "To" field was not recognized. Please make sure that all addresses are properly formed.
- sp332 6y agoI haven't found a punycode encoder that can gracefully handle an input this long, but it should be possible to make an equivalent gmail address with about 124 ACSII characters.
- sp332 6y agoI guess the problem was that the local part has a space. Let's replace it with an underscore and we get: zal_mes-55a8ss0clxz2ivbded0gccaaccafieacacagabf9af3jlfjijxcffa5e8eja5kzd9c8fxb5agq5a0d1af8fvcm5pm4a6p@gmail.com Which is 111 chars. If it allowed spaces in quotes, which is RFC-compliant: "zal mes"-4eb6x27ct1aw3j5bdccd5hecaaccabfkeacacagcabf4bf0llfggil1acffa3fyfja1m8dtd5e4a4c7agfq7a8d7af6g1cm9rm6anr@gmail.com 122 chars.