That is a totally irrelevant answer. We have a major number of small domains - few accounts, sometimes as low as 1. We do not run the unlimited license. Adding one mandatory admin to a single email domain is not a cost effective use of this one license. And no, we do not want this one email address to also be the admin of the domain.

This is pretty much a non-issue... The API also uses that primary admin when doing domain actions (that do not use the server admin) as far as I know. Get an unlimited license or move on from the issue, I dont see ST changing how SM works for this, since it clearly is not impacting the majority of it's users. I agree, it is weird, the server admin account should be able to do everything without having to impersonate etc. but it is what it is.

So, your answer to a client request is to tell the client to f*** off? WHOW. Good you do not work for smartermail.

No, my response would be, this is how SmarterMail works and further explain why we believe ST made the choice to have a primary admin. In the 20ish years we’ve used SM, we have never had a customer complain about the primary admin or even ask what it is for. so for us, it’s a non-issue.

Lol, your post got reported echoDreamz. I guess they didn't like your answer.

Matt, truth hurts I guess lol.

All, let's keep things positive and informative.  Life is too damn difficult these days!

Thomas, this question comes up occasionally and it's usually about licensing.

The domain role is essential for managing Permissions, Privileges and Scope throughout SmarterMail and the same applies to the System Admin role. This is the core of our product and has been for 20 years and it's how hundreds of products integrate with SmarterMail. Typically, domain admins are employees and use the same account as their email address. Often, there are multiple domain admins in larger organizations.

We strive to build powerful products that are  affordable and compete with much more expensive products but we realize that sometimes our products don't suit all customers. We want customers to be successful and sometimes our products are not the solution. I hope this information helps you understand things a little better and help you decide if our product is the right solution for you.

I am with Thomas on this one.  It is really annoying to have to:

1.) take the time to set up a email account that will never be used

2.) use part of the license that will never be used.

And to call it essential for managing permissions, just outlines a problem in code.  Let's consider unix for example: manages permissions where you can have user specific, but not give permissions to a group.  Or vice-versa.  Smartermail can have three groups, SU, Domain Admin, and User.  SU has access to everything, why can't we create a single user under a domain just in the "User" group?  The domain is always manageable by SU even without impersonating the domain admin user, making the domain admin pointless.  Code-wise, I can understand the concern of a domain created without anyone to manage it.  It becomes an orphan.  But that is never the case, as SU is always present. You just need a checkbox when you create the domain, "make this user a domain admin".  Else, the default, is to just make a regular user.   And if a domain requires one user else it breaks things, just need a test for deleting the last user.  This seems relatively trivial to implement.