Remove Default Email user@domain

CanadaGuy

Verified User
Joined
Nov 14, 2019
Messages
158
Is it possible to remove the default email account that is created when a domain is added? For example, if I have a DA account "user" for domain "example.com" it will create "user@example.com" email account as default that cannot be deleted from what I see.
 

CanadaGuy

Verified User
Joined
Nov 14, 2019
Messages
158
No, you can not remove the default email account.
Okay, so the "real" account associated with that email is user@server.example.com and you access it by the username/password directly without the domain attached. So account email user@domain.com is always a "special" account and forwards to the unix server account. That would be a helpful tip directly in the DA software.

Thanks!
 

Richard G

Verified User
Joined
Jul 6, 2008
Messages
5,245
Location
Maastricht
Never mind. Did not knew there was a hidden forward from user@server.example.com to user@domain.com for the unix account.
Because it uses user@domain.com that's for sure.

Just wondering, if you disable this via blackhole, system messages like Softaculous notifications must be set up seperatetaly some how? They normally are automatically send to the system account, as are quota messages etc. how about fixing that?
 

zEitEr

Super Moderator
Joined
Apr 11, 2005
Messages
14,255
Location
GMT +7.00
username@hostname and username@domain.com are identical

- username is a system account name, login to DirectAdmin
- hostname - a server's hostname
- domain.com - a domain hosted on the same server and owned by user with username
 

Richard G

Verified User
Joined
Jul 6, 2008
Messages
5,245
Location
Maastricht
I know that alex.
I just thought that it was just also vitual. I had a Postfix setup in the old days with virtual an local accounts where the locals just were implentend some way in the virtual account database and user@hostname was not reachable. I did not know DA did this with a forward.

Still wondering about my question though. When disabled via blacklist, how about quota and other system messages which are by default send to the system account (so blacklist in that case)?
 

zEitEr

Super Moderator
Joined
Apr 11, 2005
Messages
14,255
Location
GMT +7.00
If you need to read emails sent to your system account, then do not blackhole it. Simply forward emails to a virtual email account and use Sieve filters to sort emails.
 

Richard G

Verified User
Joined
Jul 6, 2008
Messages
5,245
Location
Maastricht
Oke clear. I was using auto forward to a virtual account for a long time. So that's still the best way then. Some times I got users who want those mails gone to other accounts and not use the system account. I always advise the forward or make it for them.
But it is something to think about when thinking of blacklisting the system account.
Thank you.
 

CanadaGuy

Verified User
Joined
Nov 14, 2019
Messages
158
Good thread, thanks for digging into this as it has produced much better understanding of what DA is doing.

I used a Postfix setup similar to that described above, so the local vs virtual accounts were explicitly outlined. Maybe this could be added for clarity to new users.
 

CanadaGuy

Verified User
Joined
Nov 14, 2019
Messages
158
I've been thinking a little more about this, and come to the conclusion that it leaves something to be desired. If I create a DA account "tom", then it means I cannot create an email account for a user named "tom".

Are there any good patterns people use to create DA usernames to avoid this issue? I was thinking something like "tomlocal" or "tomunix" or more generally "adminlocal" or "adminunix".
 

ditto

Verified User
Joined
Apr 27, 2009
Messages
2,580
@CanadaGuy, Even they can't create email account "tom", they can still use it as a normalt email account. They must only remember that the user name for the system account is only the username, not the entire email address.

What we do, is that we manually generate a random username for every new user, so it would not be a username they would want to use when creating email accounts. Usually we pick a username from the first and last letter in the name of the customer, or in the company name of a customer, and/or a combination of both, and if needed add a one more random character so that is become minimum 3 character.

Another thing worth mention if people a considering to backhole the system accont email, is that when users use PHP to send email without SMTP authentication, if they bounce, those email will bounce back to the system account. So I think it best not to disable it.
 

CanadaGuy

Verified User
Joined
Nov 14, 2019
Messages
158
To be more specific, I was referring to the scenario where I create DA user "tom" and he creates a bunch of domains including example.com. But then he has a client whose name is "tom" as well. In this scenario, tom@example.com would not be available to the client, as it would already be taken by DA user "tom".

Your suggestion of pseudo-random usernames is a good one as the result is usually an undesirable email address.

Yeah, I think I understand the value and use of the default user account now. It does make things a little less intuitive from the start, so emphasis on the consequences of DA username choices might be good in the documentation.
 

CanadaGuy

Verified User
Joined
Nov 14, 2019
Messages
158
What we do, is that we manually generate a random username for every new user, so it would not be a username they would want to use when creating email accounts. Usually we pick a username from the first and last letter in the name of the customer, or in the company name of a customer, and/or a combination of both, and if needed add a one more random character so that is become minimum 3 character.
This was a good tip. I did initials plus a 3 digit number for accounts. This produces accounts that are sufficiently decoupled from email address and eliminates conflicts.
 
Top