I am not at all familiar with this aspect of DNS management or even server or local locale settings, but I observe that the IDN format of the domain does not return anything, and since it is a .COM TLD, should be working, or MiaB cannot do anything, so far as I am aware.
When I input your IDN into any of my browsers (not using the hyperlinked character link in your post), the browsers change the domain being looked up to http://xn--xn1jv704d-r89d.com/. I don’t know why.
I can’t find away to look up your domain with dig or whois.
Just out of curiosity, is it possible to add a domain to MiaB using the characters?!
Thanks Openletter!
I was thinking this is just an extra domain/email parked on this MIAB and it should receive it as any other domain/email. This should be all handled by box itself nicely. It can send out email no problem though.
DNSSEC ‘DS’ record set at registrar is valid but should be updated to ECDSAP256SHA256 (see below).
show more|
|✓|Nameserver glue records are correct at registrar. [ns1/ns2.box.f2f10.com ↦ 76.10.176.225]|
|✓|Domain resolves to box’s IP address. [box.f2f10.com ↦ 76.10.176.225]|
|✓|Reverse DNS is set correctly at ISP. [76.10.176.225 ↦ box.f2f10.com]|
|✓|The DANE TLSA record for incoming mail is correct (_25._tcp.box.f2f10.com).|
|✓|Hostmaster contact address exists as a mail alias. [hostmaster@box.f2f10.com ↦ administrator@box.f2f10.com]|
|✓|Domain’s email is directed to this domain. [box.f2f10.com ↦ 10 box.f2f10.com]|
|✓|MTA-STS policy is present.|
|✓|Postmaster contact address exists as a mail alias. [postmaster@box.f2f10.com ↦ administrator@box.f2f10.com]|
|✓|Domain is not blacklisted by dbl.spamhaus.org.|
|✓|TLS (SSL) certificate is signed & valid. The certificate expires in 37 days on 2021-10-12.|
||f2f10.com|
|?|DNSSEC ‘DS’ record set at registrar is valid but should be updated to ECDSAP256SHA256 (see below).
show more|
|✓|Nameservers are set correctly at registrar. [ns1.box.f2f10.com; ns2.box.f2f10.com]|
|✓|Domain’s email is directed to this domain. [f2f10.com ↦ 10 box.f2f10.com]|
|✓|MTA-STS policy is present.|
|✓|Domain is not blacklisted by dbl.spamhaus.org.|
|✓|Domain resolves to this box’s IP address. [f2f10.com ↦ 76.10.176.225]|
|✓|TLS (SSL) certificate is signed & valid. The certificate expires in 36 days on 2021-10-11.|
|✓|www.f2f10.com: Domain resolves to this box’s IP address. [www.f2f10.com ↦ 76.10.176.225]|
|✓|www.f2f10.com: TLS (SSL) certificate is signed & valid. The certificate expires in 36 days on 2021-10-11.|
|✓|autoconfig.f2f10.com: Domain resolves to this box’s IP address. [autoconfig.f2f10.com ↦ 76.10.176.225]|
|✓|autoconfig.f2f10.com: TLS (SSL) certificate is signed & valid. The certificate expires in 22 days on 2021-09-27.|
|✓|autodiscover.f2f10.com: Domain resolves to this box’s IP address. [autodiscover.f2f10.com ↦ 76.10.176.225]|
|✓|autodiscover.f2f10.com: TLS (SSL) certificate is signed & valid. The certificate expires in 22 days on 2021-09-27.|
||peng-xiao.com|
|✓|Nameservers are set correctly at registrar. [ns1.box.f2f10.com; ns2.box.f2f10.com]|
|✓|Domain’s email is directed to this domain. [peng-xiao.com ↦ 10 box.f2f10.com]|
|✓|MTA-STS policy is present.|
|✓|Domain is not blacklisted by dbl.spamhaus.org.|
|✓|Domain resolves to this box’s IP address. [peng-xiao.com ↦ 76.10.176.225]|
|✓|TLS (SSL) certificate is signed & valid. The certificate expires in 83 days on 2021-11-27.|
|?|This domain’s DNSSEC DS record is not set. The DS record is optional. The DS record activates DNSSEC. See below for instructions.
show more|
|✓|Nameservers are set correctly at registrar. [ns1.box.f2f10.com; ns2.box.f2f10.com]|
|✓|Domain’s email is directed to this domain. [芃晓.com ↦ 10 box.f2f10.com]|
|✓|MTA-STS policy is present.|
|✓|Domain is not blacklisted by dbl.spamhaus.org.|
|✓|Domain resolves to this box’s IP address. [芃晓.com ↦ 76.10.176.225]|
|✓|TLS (SSL) certificate is signed & valid. The certificate expires in 83 days on 2021-11-27.|
|✓|www.芃晓.com: Domain resolves to this box’s IP address. [www.芃晓.com ↦ 76.10.176.225]|
|✓|www.芃晓.com: TLS (SSL) certificate is signed & valid. The certificate expires in 83 days on 2021-11-27.|
|✓|autoconfig.芃晓.com: Domain resolves to this box’s IP address. [autoconfig.芃晓.com ↦ 76.10.176.225]|
|✓|autoconfig.芃晓.com: TLS (SSL) certificate is signed & valid. The certificate expires in 83 days on 2021-11-27.|
|✓|autodiscover.芃晓.com: Domain resolves to this box’s IP address. [autodiscover.芃晓.com ↦ 76.10.176.225]|
|✓|autodiscover.芃晓.com: TLS (SSL) certificate is signed & valid. The certificate expires in 83 days on 2021-11-27.|
Also, I discovered the issue with the character domain on MiaB seems to be the dig version, because curl works just fine, so it is at least supported by the OS.
And have you tried emailing the address from other mail servers outside of your own?
I meant to communicate trying to send an email from a server that is not the MiaB server and not a Google server, such as example@hotmail.com to an email address of the character domain. Because it seems so far you have only communicated a problem receiving mail from a Google server.
I did some research into what is happening. We use Dovecot to manage mailboxes, and Dovecot does not appear to support “SMTPUTF8” which is a recent-ish addition to email protocols for supporting Unicode, i.e. internationalized email addresses.
What we’ll do in Mail-in-a-Box going forward is turn off SMTPUTF8 support in Postfix. This will signal to senders (like Gmail) that an internationalized address is not supported, and Gmail will instead send the email using the IDNA form (@xn--...), which doesn’t look as nice in your mailbox, but at least the email can be received. (I just tested this.)
This may have the downside that Mail-in-a-Box users might be sending SMTPUTF8-requiring outbound emails, which will stop working. I don’t think we can have it both ways (esp. since an outbound email might be an email to an internationalized domain hosted by the box itself). I’m not sure.
(While researching this, I noticed that the “relay access denied” error could be fixed so that it gives a more informative error in the bounce (“SMTPUTF8 is required, but was not offered”) without disabling SMTPUTF8, by letting Postfix know we also should be receiving email for the Unicode form of the domain. But after I discovered that disabling SMTPUTF8 makes the emails deliverable, that seemed preferable.)
