> Hello,
>
> We are finally getting around to rolling out the new QmailAdmin/Vpopmail
> to all of our clients and we have received some suggestions on the
> QmailAdmin interface. I wanted to run them by the people on the list to
> see if these are features that others would like to see or not.  If they
> are, I will release a patch.
>
> The first feature is the ability for a non-postmaster user to be able to
> see their disk usage when the log into the QmailAdmin interface.

I have had this question too, great.

> The second feature is just a simple modification.  It has been brought
> to my attention that some people do not like putting in NOQUOTA when
> they wish a user to not have a quota set.  I had chosen to use NOQUOTA
> in the 1.0.4 patch out of pure laziness, so I take full blame.  It would
> be just as easy to have the users just leave the quota field blank for
> no quota.  It's a minor thing, but I could see how it would get annoying
> to have to type in NOQUOTA when leaving it blank makes better sense.

INHO leaving this field blank should default to the default quota. Anything
else would mean extra work for the postmasters, as 100% of the users use the
default quota. In my opinion a N instead of NOQUOTA in this field, would be
nice for no quota.

Another thing the postmasters have mentioned is the location of the quota
field. They think it should be placed below the real name field. They never
put anything in the quota field, so this would save them a <TAB>.

One last thing, which I think is quite funny.
Some users have complained about not being able to log in to Qmailadmin. As
the default User account in the login window is postmaster, they think they
are about to log in as postmaster for their own account, supplying only their
password. Luckily there are not many users who are this clueless ;-)

Personally I think it would be more logical with the domain name as the
uppermost field in the login window.

I have also had requests for a link to the help-files in the add mailinglist
window.


--
JKvalvaag


Reply via email to