think tank forum

so i registed a domain under the new shabaka gTLD.

this tld is an arabic tld. open reg no crazy requirements.

the shabaka gtld translates roughly to network.

so i registered the arabic word for terrorism on that tld.

then i created a unicode user on a linux box and setup postfix / mutt.

now i have this email address working.

مفتوح.ذبابة@إرهاب.شبكة

of course, working is a relative term. pretty much NOTHING can handle it. google is HORRENDOUSLY broken with IDN and unicode names.

the unicode in the username throws up errors on their smtp servers. the IDN isn't translated by their email servers, or clients, and you cannot send or reply to emails from them. It assumes they aren't valid email addresses.

outlook only barfs on the unicode username. it replies to emails with ????? in place of the unicode.

it oddly enough handles the IDN fine. placing it in a class with mutt by themselves.

mutt handles everything perfectly.

so far... nothing else does. i am going to setup an email on this domain and put it on business cards... just to have an email that is an unmitigated fucking nightmare to try and send email to and receive email back from.

heh. Actually, this doesn't really surprise me tough... We still have a long way to go for proper unicode support. Many, *many* tools are still broken.

hahaha this is excellent. I'm gonna try to email you.

Fastmail.fm webinterface: fails

ssmtp: RCPT TO:<مفتوح.ذبابة@إرهاب.شبكة> (501 5.1.3 Bad recipient address syntax)

This sounds like a really good anti-spam solution by the way.

well I made sure utf-8 was enabled on debian and in putty but it still didn't work. maybe it's the font I'm using? I don't think windows has any fixed width fonts that will work...

that's not true consolas seems to work fine in notepad but not in putty? courier new works pasting at the shell prompt but I can't get the address to paste into mutt.

roundcube/gandi.net fail http://i.imgur.com/zTyO1Xc.png

putty needs to be switched to utf-8 it defaults to an ascii console. but it has utf-8 support.

i am missing utf-8 extension support in postfix on my mail server atm. not sure i want to support that rfc. way i see it is posix is utf-8 compliant... should NEED utf-8 extensibility. and postfix sure as shit doesn't. mutt doesn't. but i can kinda see why no one wanted to just let people start sending UTF-8 encoded usernames through their mailservers.

kinda the same reason dns swapped to punycode.

=/

anyways fun translation hilarity.. was going to give myself the arabic translation of matt@terrorism.network. found out matt translates to the same word used for the arabic word die.

so matt@terrorism.network in arabic is the same as die@terrorism.network.

مت@إرهاب.شبكة

boss email.

putty's on utf-8. seems like it's mutt's problem, perhaps with bidirectional text.

make sure you have a recent version. also check the term environment on the unix box.

ttf certainly doesn't like it... probably because it requires a "." after the "@", and it reads left to right.

yeah... that does throw it off a bit.

also... seems RFC6531 is a bust in postfix...

RFC 2047 may be made to work... though i have no idea how. but when it comes right down to it... there's no stable and supported protocol for unicode recpients in email.

primarily because MTA devs are racist fuckwits.