Domain eposta.orutbag.com already exists

Cem

Hello folks,

I have tried add my mx domain to mailcow but it gave some error (I didn’t saved it). Then tried to recreate the domain now it gives “Domain eposta.orutbag.com already exists” but it does not show up on the list. I guess, it is a bug but I am not sure so I didn’t report it as bug.

any help appreciated…

esackbauer

Create where? maybe you have added it already as alias domain?

Cem

I have added as domain but it didn’t created due it’s same as hostname. So, I have added it as alias. I couldn’t find it on the alias list but after your response I have checked it, it is added as alias. Thank you. Now, my question is how can I have FQDN email address?

esackbauer

You need a lot to learn about DNS with mail servers.
There is no such thing as “FQDN email address”.
Please read again the DNS requirements, and learn how MX, CNAME and A records work and what is their purpose, otherwise your mailserver will be a desaster.
https://docs.mailcow.email/getstarted/prerequisite-dns/

Cem

esackbauer hi, it’s about my language. I meant how can I create email address from FQDN hostname? To be more clear, how can I create cem@eposta.orutbag.com. Currently, when I try to create domain within that address mailcow throws error. The error is “Domain cannot match hostname”.

Btw, I made the all necessary setup for dns and checked, I guess they are all set however if you see an error on the configuration from my email server please let me know as you are experienced about email servers your help appreciated. Thank you anyway for your all support.

best regards,

esackbauer

Cem The error is “Domain cannot match hostname”.

This is showing that you have not really understood how the DNS records work and what their purpose is in context to a mail server.
The FQDN hostname should never be the same as a mail domain (MX record), and that is why you get the error message.
Change the hostname, adapt the MX records and A record, and change hostname in mailcow.conf, do docker compose down && docker compose up -d, wait some time until A records have been properly published in DNS, force ACME container to renew certificates, and it should be OK.