on 7/13/01 1:17 AM, Ken Jones at [EMAIL PROTECTED] spake:
> Bill Shupp wrote:
>>
>> Here are the "TODO's" I'm aware of before a 1.0 release:
>>
>> 1. Enhancements to modify user screen (Ken Jones)
>> 2. Possible merging of aliases and forwards
> I can do this one unless someone else wants to.
>
>> 3. Finish up modify ezmlm-idx lists (Bill Shupp)
>> 4. Allow multiple ezmlm subscriptions at once, either via <textarea> (copy
>> and paste) or uploading of a text file. (Brad Dameron?)
>
> 5. Update pages so they stay on the same screen after modifications
> (Ken)
I like this idea.
> 6. Change authentication scheme to use cookies instead of Time/IP (Ken)
>
> What do you guys think about using cookies instead? People behind
> proxies or NAT gateways can't use qmailadmin since thier IP changes
> during thier session.
I've always thought it was cool that qmailadmin *didn't* use cookies. But
I'm not behind a proxy, and none of my customers have complained about that
yet.
> 7. Review the MaxXXX qmailadmin-limit code for disabling of features
> (Ken)
> I want to check this over and test it again. With Forwards available
> under a user account and also available to the postmaster off the
> main
> menu, some sites may get confused by it. So it would be nice to be
> able to turn it on or off in the qmailadmin-limits file.
It might be cool to allow qmailadmin-limits to specify a "default gid" when
creating accounts.. Say "allow_imap no" or something like that.. so when
the postmaster uses qmailadmin to create pop accounts, all those accounts
have imap access disabled.
Which brings me to another question... since services can now be
enabled/disabled by the gid field (moduser), have you thought about updated
the vadduser part of the API to allow for this? Right now, you have to use
moduser to make these changes. Might be cool for vadduser (and other apps
through the API) to be able to specify what services are enabled when
calling vadduser.
Cheers,
Bill Shupp
