implement tools to combat spam when sent from scripts hosted on domains.
We would like customers to manage their domains themselves but limit them to a list of domains defined by the reseller/admin.
It would be great if a customer could e.g. define himself which domain (alias) should belong to which hosting package.
The problem at the moment is: If we give customer A the privileges to manage his domains, he could also add a foreign domain (NOT on the server) and configure mail accounts, e.g. *@ebay.com. The result would be that any mail another customer B who also uses our server sends to this domain could be "captured" by customer A.…
2
votes
Anonymous
shared this idea
Unfortunately, we have to close your request, because over the years it has not become quite popular for further implementation.
—
IG