Hello
I just reserved a domain name. An email address is associated with the package. I assume that creating the mail must go through Zimbra. I chose the name as a prefix, but Zimbra gives me an address that doesn’t really resemble the reserved domain name. For example, the domain is hemcé-conseil.fr and Zimbra shows me hemcé-conseil.fr
A kind and knowledgeable person could help me?
Hi,
I don’t quite understand your problem because hemcé-conseil.fr seems to be your domain name (repeated twice in your message).
I strongly advise against using a domain with accents.
Horror @OlivierM70
Your domain hemcé-conseil.fr contains accented characters. 
Hello
Indeed you see it correctly but I see it like this
And I don't really know what to do with this.
Hello @OlivierM70
It's inevitable when you register a domain name with an accent; emails can't have accents and are re‑encoded.
The only solution is to register the domain without an accent hemce-conseil.fr as soon as possible if it is available.
It’s the accent… Don’t use this domain but the one without the accent (reserve it quickly).
OK.
Thank you all.
But then why propose accented domain names? Is it possible to use an accented name for a site? And not possible for an email?
We don’t propose it to you; you’re the one who asks for it, it isn’t forbidden, we’re supposed to know the consequences.
A browser knows how to interpret the encoding; the proof is that you wrote it with the encoded accent, but the browser displayed it with the accent in your message. An email client doesn’t have the functions of a browser.
A web rule: never use accents or special characters in file, directory, or domain names; even if it’s possible, it should be avoided.
Other languages are more sensitive to accents than French.
For example, writing in German: Koln instead of Köln is a mistake. At most, Koeln.
The day when Mr. Duçon and Mr. Grosçon invented the cedilla…
So if you’re interested, research “IDN domains” and punycode.
In 2012 I wrote the very first post on my blog: https://blog.demees.net/hello-world/
But then why offer accented domain names?
For the money?
hi,
It's not any more expensive, though.
However, I've read that accented addresses make a noticeable difference in marketing. It might be good for a website address but not okay for an email address.
Honestly, apart from domain protection (and even that) I don't see any benefit. I don't know any service that uses a domain with accents.
I recommend using the same domain for your site and your email addresses 
Hello @OlivierM70
In short, it’s to get you to buy both domains: the one with the accent and the one without the accent.
Set up your entire site using the domain without the accent. Then, via multisite, point the domain with the accent to the www folder of the domain without the accent.
I’m going to tell you a very Belgian story.
Shortly before Covid, the Belgian authorities set up a computerized medical record.
Each citizen has access to his record referenced by a unique key, the national number.
The medical corps also has access.
(here I’m not going to discuss the inherent risk of asking authorities to keep “en bon père de famille” sensitive files.
We’ve seen what that looks like in France)
So I was saying: digital medical record.
The authorities chose a domain name “Ma Santé”, which naturally becomes https://masanté.be (with the accent)
It should be noted that the same domain name, without the accent, has already belonged to a parapharmacy company for over 20 years!
The domain masanté.be still exists, and redirects to a more authentic site https://www.masante.belgique.be/ … it’s better that way, after all.
The company in question has certainly appreciated the influx of new visitors.
It’s clearer with this good illustration! Thanks. I understand better.
I reserved the domain name without an accent; indeed, buying it twice isn’t very useful because I don’t think I need a website, especially since I wouldn’t know how to create one. I’ll only use the email address.
Hello. Accented characters are perfectly legal in domain names and are indeed replaced by --xn etc. Modern browsers handle that very well and display the accented characters even when they are encoded as --xn. However, I don’t know whether email clients like Thunderbird are aware of this, because I have never encountered the issue for them.
More details at https://www.afnic.fr/observatoire-ressources/papier-expert/peut-on-avoir-des-caracteres-composes-dans-un-nom-de-domaine/
I’ve made multiple attempts for the email. In short, it doesn’t work. In 2005 we hoped to fix it within a few years. Nada.
Or rather I should say it only works with punycode notation “xn--”!