[olsgaarddk]

Does anyone on HN have any of these "surprising" email addresses that most people and developers do not expect?

How does it work with common e-mail clients? How do people react when you show/tell them your email?

I have a domain that uses non-ascii characters, and while I can receive emails on that domain, hosted by Fastmail, Fastmail clients refuses to _send_ emails to that domain (I can, if I type the domain as Punycode).

[jmkni]

I have my own domain and a catch-all setup, so when I sign up for a service, it's [e-mail], if I give someone my email address, it's [e-mail]

It makes it easy for me to keep track of who is sending me what + who is sharing my email with third parties, but definitely confuses some people.

[jeroenhd]

Samsung is particularly annoying about this. You can't sign up for an account with "Samsung" in the user portion. They'll straight up block [e-mail], so I've resorted to misspelling their name in the email address and they seem perfectly fine with that.

[sidharthv]

I've been using sam.sung@domain for them. First time I've come across this block in years of using this method.

[krageon]

> Does anyone on HN have any of these "surprising" email addresses that most people and developers do not expect?

I do

> How does it work with common e-mail clients?

Perfectly

> How do people react when you show/tell them your email?

With confusion, so it requires some gentle insistence that I know my own email address.

[kingcharles]

I can't type one of my email address on HN as it has emojis in the hostname. It works great with Fastmail. It gets problematic when I use emojis in the mailbox name as well. At lot of hosts won't allow that.

You can see the email address on the front page if I paste the punycode web address on here:

https://xn--bp8hgh.to/

[jeroenhd]

Messing with emoji taught me how absolutely atrocious unicode support among email servers is. Gmail supports it, but even modern versions of postfix require special compilation flags to enable SMTPUTF8.

While emoji aren't a use case you'll get many managers to care about, there are plenty of unicode characters that can. Email addresses using foreign script, for one, or even just characters like åäáà, not uncommon in European names, might convince people to consider enabling such features.

Sadly, the process of enabling support for such characters is much harder than it should and I've got to admit they my mail infrastructure also can't handle these types of email addresses. Modern MS Exchange servers seem to have finally implemented support, though, so perhaps we may see more support for it in the future!

[Avamander]

I think postfix's DB drivers were also still latin-1 only, if I'm not misremembering I had to mojibake what I wanted it to pick up.

Though UTF-8 is not the only thing atrocious with e-mail stacks, there's so much maintained-but-not-really non-standard software that a lot of people rely on.

To end on a positive note, e-mail hosts are starting to demand SPF to accept mail.

[spoils19]

I do and like many other HN users, when websites refuse to accept my email, I simply don't use their service. I haven't noticed any decrease in my quality of life - in fact, being able to use my email freely is invigorating and gives me a sense of worth in this corporate controlled internet.