error: Multiple Domains sharing one email folder in Admin account.

[Hetzner DirectAdmin]

I installed DA on Debian 13 and noticed that when I create multiple domains in the admin account, the emails from all the domains are sharing one inbox.

So if I send an email on one domain, the other 7 domains receive the same email.

So then I reinstalled DA on CentOS Stream 10 and I got the same error.

All mx, DKIM SPF and other DNS entries are correct.

Each domain is pointing to its own mx record.

 

[zEitEr]

did you create domains as aliases/forwarders?

 

[Hetzner DirectAdmin]

did you create domains as aliases/forwarders?

That is a very interesting question you pose, I was reading about this possibility, but I can't imagine this being the case. I would love to explore it though.

I done this process on someone else's mxroute.com DA servers and everything worked correctly. I can't figure out why this is happening on my instance.

After fresh DA install, I log in as administrator and there are no domains.

As an example, my DA is https://www.fiefdom.com:2222

1) I click USER tab and create a domain fiefdom.com
2) I goto email and the default email is created as [email protected]
3) I enable DKIM and proceed to plug in the DNS records on Hetzner Console.
4) I can send/recieve emails with 10/10 from mailtester.com

So far all is just great.

I have two other domains I want to add now. So, i did:

5) USER->Domain Setup->add new domain and I add the domain knights.com
6) I enable DKIM and proceed to plug in the DNS records on Hetzner Console.
7) This time i setup mx 10 mail.knights.com (I wonder if I should use mail.fiefdom.com)
8) I can send/recieve emails with 10/10 from mailtester.com

When I log in with an unassociated gmail account and send an email to [email protected] then [email protected] also gets it.

If I erase that sent email from the [email protected] then it is automatically deleted on [email protected].

It is like they are sharing the same inbox and this is a fresh install, so I can't see why this is happening

 

[zEitEr]

This is the default email account, which is shared across all domains under the same directadmin account. It is based on:

<dausername>@<userdomain>

and will work even as

<dausername>@<hostname>

so if you create any additional separate email account on any of the domains, they will have its own storage and settings.

 

[Hetzner DirectAdmin]

did you create domains as aliases/forwarders?

I also realised. If I were to change the password for [email protected] it would automatically change the password for [email protected]

 

[DrWizzle]

I also realised. If I were to change the password for [email protected] it would automatically change the password for [email protected]

If you want emails such as [email protected] and [email protected], my suggestion would be to run the username change script (/usr/local/directadmin/scripts/change_username.sh) and change admin to something else you're not going to forget or use as an email address. It help security and also sorts out the ambiguity of the admin email default inbox.

Once you've done that, mail should start hitting each box properly.

 

[Hetzner DirectAdmin]

This is the default email account, which is shared across all domains under the same directadmin account. It is based on:

<dausername>@<userdomain>

and will work even as

<dausername>@<hostname>

so if you create any additional separate email account on any of the domains, they will have its own storage and settings.

Oh wow, I have been having so much confusion about this for weeks. These first steps might be what I am doing wrong, and need to understand.

If you want emails such as [email protected] and [email protected], my suggestion would be to run the username change script (/usr/local/directadmin/scripts/change_username.sh) and change admin to something else you're not going to forget or use as an email address. It help security and also sorts out the ambiguity of the admin email default inbox.

Once you've done that, mail should start hitting each box properly.

Hiya @DrWizzle , thank you for the reply.

I do not need admin@ for any of my domains, it was just the default after a fresh install, so I just went with it, that's all.

@zEitEr I think has figured out what I have done wrong

This is the default email account, which is shared across all domains under the same directadmin account. It is based on:
<dausername>@<userdomain>
and will work even as
<dausername>@<hostname>
so if you create any additional separate email account on any of the domains, they will have its own storage and settings

Oh wow, I have been having so much confusion about this for weeks.
These first steps might be what I am doing wrong, and need to understand.
I am just missing the initial context on how I am supposed to apply this.

I am the only user of DA, my domains, and my emails.

I recently bought fiefdom.com plus an SSL certificate exclusively for using DirectAdmin.

So, I install DA, I chose www.fiefdom.com as the hostname so the SSL would work. (i dont like lets encrypt, my X worked there)

Once the initial Custom Build is complete, I create a new user with unlimited access?

and then proceed to start creating domains under that new user. Is that how I am supposed to begin with a new install?

Thanks guys, you are great !

 

[Hetzner DirectAdmin]

So if you create any additional separate email account on any of the domains, they will have its own storage and settings.

Ok, I understood you now! Wow, that is really smart actually.

Just off topic. Is it okay that I choose www as a hostname? Is there any obvious destructive, end of the world reason I should not do that?

 

[zEitEr]

Just off topic. Is it okay that I choose www as a hostname? Is there any obvious destructive, end of the world reason I should not do that?

If you plan to host a website in www. then you might choose another hostname, like: server.domain.com, or anything-else.domain.com

 

[DrWizzle]

Oh wow, I have been having so much confusion about this for weeks. These first steps might be what I am doing wrong, and need to understand.


Hiya @DrWizzle , thank you for the reply.

I do not need admin@ for any of my domains, it was just the default after a fresh install, so I just went with it, that's all.

@zEitEr I think has figured out what I have done wrong



Oh wow, I have been having so much confusion about this for weeks.
These first steps might be what I am doing wrong, and need to understand.
I am just missing the initial context on how I am supposed to apply this.

I am the only user of DA, my domains, and my emails.

I recently bought fiefdom.com plus an SSL certificate exclusively for using DirectAdmin.

So, I install DA, I chose www.fiefdom.com as the hostname so the SSL would work. (i dont like lets encrypt, my X worked there)

Once the initial Custom Build is complete, I create a new user with unlimited access?

and then proceed to start creating domains under that new user. Is that how I am supposed to begin with a new install?

Thanks guys, you are great !

Hi @Hetzner DirectAdmin ,

A word of warning here. Don't call your server hostname "www.domain.com" as it may conflict with apache or whatever you're using.

Call your server anythingyouwant.domain.com , create an A record to match this name at Hetzner, and set your rDNS on IPv4 and IPv6 to this name also at Hetzner under "Networking" tab. (In the IPv6, create rDNS as 2a01:4fX:XXXX:XXXX::1) and don't forget to add the IP in your IP management section of DA Admin panel, and link it to your IPv4 for perfect connectivity.

Sorry if this seems a faff, but it's imperative for perfect mail delivery and DNS resolution.

 

[DrWizzle]

I recently bought fiefdom.com plus an SSL certificate exclusively for using DirectAdmin.

So, I install DA, I chose www.fiefdom.com as the hostname so the SSL would work. (i dont like lets encrypt, my X worked there)

Once the initial Custom Build is complete, I create a new user with unlimited access?

and then proceed to start creating domains under that new user. Is that how I am supposed to begin with a new install?

Thanks guys, you are great !

I've no issue using LetsEncrypt for the TLS and a few smaller play sites, but I bought an OV Cert for the Company's site and use a 3rd party mail service and their SSL for that.

 

[Hetzner DirectAdmin]

and use a 3rd party mail service and their SSL for that.

L0L, that reminds me of the monstrous headaches that Levison had a decade ago. I think there is more of that to come with HMRC's new lusty desire to scrape for data coupled with Canada's introduction of tele-warrants back in 2020.

The faff is much welcomed, since now is the time to make that call of using the www hostname. For my puposes wildcards are too pricey, but I guess I could buy another DV for server.fiefdom.com.

@zEitEr said

If you plan to host a website in www. then you might choose another hostname, like: server.domain.com, or anything-else.domain.com

I actually domain pointed fiefdom.com to www.fiefdom.com:2222 and the only site I want to host is DA.

Having said that, I have to heavily consider the enlighting "faff" offered by @DrWizzle as email stability is of paramount importance to me.

 

[DrWizzle]

L0L, that reminds me of the monstrous headaches that Levison had a decade ago. I think there is more of that to come with HMRC's new lusty desire to scrape for data coupled with Canada's introduction of tele-warrants back in 2020.

The faff is much welcomed, since now is the time to make that call of using the www hostname. For my puposes wildcards are too pricey, but I guess I could buy another DV for server.fiefdom.com.

@zEitEr said


I actually domain pointed fiefdom.com to www.fiefdom.com:2222 and the only site I want to host is DA.

Having said that, I have to heavily consider the enlighting "faff" offered by @DrWizzle as email stability is of paramount importance to me.

DV Wildcard certs aren't that pricey, but then again I guess it all depends what your budget is. I've an OV non wildcard and that was expensive enough. It's your call but as @zEitEr said though also, please consider calling your hostname something other than WWW. I trust @zEitEr 1000% on here as he is one of the authorities in speaking for DirectAdmin and Linux in general. If you only have a DV to secure the hostname, you can always have it issued as hostname.domain.com. Also consider using a wildcard free cert from ZeroSSL (Built into DA) if you're not comfortable with LetsEncrypt. Don't forget also the TLS cert for the server hostname also secures your mail server and other services as it's all linked.

All the best!