ACL's

**kgordon** · 05-26-2004 02:07 PM

I'd like to see ACL's in cpanel much like we have for WHM. That way we can control exactly what features a specific client can see. Instead of someone trying to make a mailing list and it saying something like 'you have no mailing list access' it can just hide the icon. When we build packages we can control exactly what features a customer may have access too. The current feature administration for cpanel is too limited, and again, should be more like the feature control ACL's for WHM

**largolam** · 06-02-2004 03:25 AM

Heres an idea. People who try to set their default address to :fail: invariably enter just :fail or fail: or even just fail.

Instead of requiring a user to actually type this in, why not just have a pulldown or button labelled 'reject mail sent to addresses I havent created', that would set it properly automatically. (It should be a seperate form/submit button that the form handler would recognize - no javascript or similiar nonsense)

Also, it should be set to :fail: by default on a new account, and for that matter, on added domains and subdomains, as well - as someone else mentioned, a newly created hosting account should not accept any email until the account owner creates mailboxes. (Of course, the various things that send from random made-up addresses in users domains would need to be changed as well to use addresses known to be valid)

Or at least have a tweak in WHM to make it this way.

I echo the request to get rid of the non-virtual 'main account' mailbox, but that may be a difficult migration. At the very least, setting new accounts to not automatically dump spam and virii there would be a good step in that direction (new accounts set to :fail:) Possibly have a 'hide main account' tweak in WHM (which would also block POP/IMAP access to is) so we can set that on new servers to accomplish the 'effect' of getting rid of the main, while still leaving it there for everyone thats already using it on existing servers.

With this change, the default address form input handler, should validate the input, and refuse to set one without an "@" in it. People will create an account, and then (since the default setting of it had the main account, with no domain), will enter just the username part of the account, which will try to deliver it to that nonvirtual user )which may or may not exist) instead of the virtual account they created.

Yes this will prevent ever setting the default back to the main except by hand - I consider that a desirable feature.

**B12Org** · 06-21-2004 12:26 AM

usernames that can start with a number would be a very nice addition

Like for those of us who use scripts to setup users and choose their usernames based on their domain name, when their domain name starts with a number it really screws things up.

**largolam** · 06-21-2004 12:42 AM

Usernames that start with a number would be bad.

If they are to be used in the /etc/passwd file, usernames should be required to

- start with a letter

- consist of letters and numbers only

- consist of *lowercase* letters only.

- be a maximum of 8 characters

**orb_sp** · 06-21-2004 12:42 AM

How about adding openwebmail to the webmail programs again. It is a much more feature rich product that any of the 3 currently provided and has been mentioned by many in this thread.

**wential** · 06-21-2004 02:01 AM

I'd settle for a working Windows version.

**B12Org** · 06-21-2004 09:56 AM

Originally posted by largolam
Usernames that start with a number would be bad.

If they are to be used in the /etc/passwd file, usernames should be required to

- start with a letter

- consist of letters and numbers only

- consist of *lowercase* letters only.

- be a maximum of 8 characters

As long as domains can start with a number, usernames should be able to as well.

**largolam** · 06-21-2004 10:10 AM

Originally posted by B12Org
As long as domains can start with a number, usernames should be able to as well.

What is appropriate for a unix system username has no relation to what might be appropriate for a domain name. Now if cpanel were to redesign so that the hosting account usernames were *not* also unix account names, then that would be fine.

Perhaps this should be yet another set of 'tweak' options, so that individual admins can choose what restrictions they want placed on usernames. Either that, or cpanel could implement 'hooks', so that you could specify a locally-written script that should be called immediately prior to account creation, that would be passed all of the information about the proposed account, and it would be able to return an 'ok'/'not ok' status (and possibly some explanatory text for a 'not ok')

On a side note, originally domains weren't allowed to start (or end) with a number either, but that was relaxed so NetSol could make more money.

**B12Org** · 06-21-2004 10:35 AM

Gotta love verisign

**dysk** · 06-28-2004 11:59 PM

Hi All,
I personally think that cPanel has enough features already. I mean, new toys are always nice, but most important to me is that there are only as many features as there are resources to maintain and support them.
I would love to see a reimplentation with the same features, but with better organized code. Maybe some people disagree with me, but frankly the current cPanel source tree is a mess.

What I would love to see in cPanel Pro is:
* Less frequent updates with much more QA and thought going into each update.
I seriously wouldn't mind if cPanel was only updated quarterly, with serious security updates coming as necessary. This would give a lot more time to test out every feature, and how they work together. Then send out (even by email) a detailed list of changes, and give people the option to upgrade when they're ready.

* Lots of ability to customize it.
-- I would actually prefer if some of the details were in a configuration file instead of the main interface, but all of the configuration files need to be well documented.
I don't mean superficial options. I would love to see very few things hardcoded into cpanel.
For example, say that I wanted to change the template cPanel uses for creating DNS zones, I'd love there to be a configuration file or template that I could do that in.
Or what if I wanted cPanel to add another directive into the apache configuration for each domain it creates? That should also be possible.
I know this sounds like an almost impossible order, but so many other programs offer this level of customizability. Look at Exim.

* More options in the RPM update scripts. Frankly I'd rather do my own rpm updates, but as long as cPanel does it, it might as well do it right. Maybe a page with the current version installed, the latest version, and a button to upgrade to that version.

* Scrap the linkage between subdomains and addon domains. It adds an awful lot of obfuscation to have a subdomain for every single addon domain.

In summary, I would love to see cPanel Pro as a tool for people who aren't afraid of unix and everything it can do, but want something to automate their daily administration and customer service.

Best Regards,
Erek Dyskant
Unix Consultant

**VagaStorm** · 07-14-2004 11:32 AM

What is the difference between 1.0 pro and 9.x regular?

What I would most like to see is some way to cluster servers and have one access point to all of them.
I would also like to be able to add windows servers to that cluster

unfortunately, allot of my customers want windows.

We currently use helm on our windows servers, and probably sometime next year it will support linux. I for one would rather see all my servers running cpanel/whm than helm

**hariskhan** · 07-17-2004 05:23 AM

Hello

Some MUCH NEEDED fixes, and some features...

1) You logout of cpanel (the session doesn't expire), type the cpanel's URL, and without asking you user/pass again, it takes you back in.

(No session handling in cpanel?). Some links in cpanel are javascript:go(history-1); Change it to legitamate?

2) When a new account is created.. there should be an option to send an auto-generated mail to the customer (if a contact address is specified). There should be a checkbox there, whether to auto-send a mail to the customer that their account has been created. The admin, creating the account, should have an option to edit the contents, format of the auto-generated mail being sent to the customer.

3) Feature activate/de-activate form for normal cPanel users (Allow some customers to see some features and not see others in their cpanel). If admins disallowed SSL, the option should not show up in customer's cpanel. This type of thing.. Right now, any customer can just create an SSL certificate for them from their cpanel, without me/admin allowing them to do so.

4) Mailman, mailing list (Still doesn't work, why?)

(Create a list, it says, it has created it, but its nowhere, you list them and cpanel says, no mailing lists defined).

5) Make Exim use the ./Maildir/ format by default (or least keep it as an option). ./Maildir/ way of mailing is safer, faster and the mailbox is never busy to receive new mail. (I don't know if ./Maildir/ supports emails for addon domains and parked domains and their sub-domains, I hope it does)

6) Exim quota.

If an email address passes its quota, its mails should bounce and a mail should be sent to root/admin of server. There should be a softlimit for mailbox quota (when the warning is sent), and then a hard limit when everything just bounces back. (atm, it just allows the customer to use-up as much space as they can in mails).

7) Fantastico doesn't install right. The admin panel, when one configures it, after that it just goes off. (I changed its style of reporting and after that couldn't see anything. In its UI, combo boxes were just empty).

8) Addon domains, parked domains have issues with httpd.conf, when removed. It doesn't do a clean removal of the domain from there.

9) Web Stats, Urchin. Admin is not able to see any stats, because for the admin, Urchin can't process the logs, while customers can see their reports just fine. Maybe a file permissions problem (Fix this!!) in /usr/local/apache/domlogs/files can't be accessed by nobody/nobody.

10) The shopping cart's a waste when it comes to UI, which can be recolutionized through CSS.

11) Account transfer, copies the UID (from the old) to the new system too. For e.g. I have no users, no customers (I can start creating accounts on a fresh linux box with UID 150), but when I transfer an account, which had a UID 32359, it creates the user with the same UID on my system, and the next time I create an account, its UID is 32360. Why waste all those UIDs from 150 - 32000? Why does it need to copy the UID too? Can't it set permissions AFTER it has transferred all the files and mails and settings?

12) Make those icons look orderly (not like they are shown right now). In a nice order means.. show them all in the same size. Be it text or icon. Some option look small, others look bix. Its the same as if I was telling you to make the text paragraph "justified" (all lines end at the same place), rather than left aligned (which would have some of the lines ending earlier than the others in the same paragraph).

If its not possible, remove the text that comes with the icons and put them in the "title" attribute of the hyperlinks of those icons. That would make them appear as a popup, which would look awesome.

Talking of icons.. and styles, will you PLEASE!!! do something about the options in the left frame of WHM? The options in small text, "look" aweful! Put small icons (transparent) on the left of the text with them.

13) (Optional) Make those Icons (WHM, cPanel) transparent and shiny

Apart from the optional shining up the icons part, there are too many fixes needed in cpanel. I can go on and on about them. When are you guys going to fix them?

**largolam** · 07-17-2004 07:56 PM

> If its not possible, remove the text that comes with the icons and put them in the
> "title" attribute of the hyperlinks of those icons. That would make them appear as a
> popup, which would look awesome.

GOD NO, do not do this. I dont want to have to remember what each of the pictures mean, or have to hover my mouse over each one to find something. If anything, get rid of the useless pictures, and make the text links larger so they are easier to find. Order them in some more meaninful way too.

We dont need shiny or pretty. Cpanel/WHM has plenty of that. Concentrate on 'more reliable', 'more stable', 'easier to use'. Please dont any more shiny pretty fluff.

For instance an 'easier to use' addition would be, add an account search box right on the main page that comes up, to enable someone hitting WHM to immediately look up an account without having to hit 'Accounts', 'list accounts', wait for that to load then finding the lookup.

**Sanford** · 07-18-2004 01:39 AM

BoxTrapper:

1) Ability to block an entire TLD ( \.ru or \.kr , etc) -- I use these with "from" and sometimes it works, other times it doesn't.

2) A Multiple select to delete/add/ignore in the Boxtrapper Queue.

3) No "blank" lines in the Revies Log form.

SA:
Ability to "grammar check" for MAJOR misspellings and word that don't match. (Some new trick(?) from the spammers.)

Does anyone use FINGER any more? Could sure help reduce some spam.