Re: [Mailadmin-devel] Re: Freeze on 1.5.x, call for features on 2.0

[James A. P. <ja...@pc...>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Chris Bowlby wrote:
| At 06:38 PM 3/29/04, Chris Bowlby wrote:
|
|> Hi All,
|>
|>  Ok, now that 1.5.2 is out the door, I'd like to retire that package
|> so we can work on a newer version that is much more flexible, and can
|> be configured fairly easily. 1.5.x I'd like to leave as a bug fix only
|> version with new versions going into a 2.x version. This is what I'd
|> like to have as part of my wish list:
|>
|> - Change to a session based platform, rather then cookie based. Cookie
|> usage is outdated when dealing with PHP and sessions are much easier
|> to maintain.
|> - A flow based means to manage ACL controls on folders, for both
|> cyrus+sasl and cyrus2+sasl2 based systems. James started some work on
|> this area based on older work that I had in place, but we both felt
|> 1.5.x based ACL controls were going to be somewhat limited anyway.
|> - fully PHP based, remove as much of the perl code as possible. I
|> don't yet know if this will be possible, but I'd like to remove some
|> of the issues we've been having with SUID based scripts.
|> - I new interface, allowing administrators to move around the system a
|> little easier.
|> - Give the user (non-admin accounts) more control over their own
|> mailboxes....
|> - Change in the file structure framework, so that we can simplify some
|> screens a little more.
|>
|>  This is a small wish list, but it's also a set of ideas I've been
|> thinking about for the last year or so, anyone have any additional
|> items to add?

Adding support for ldap or other authentication backends where we would create
users in them and not the sasl interface, but the rest of the functionality is
still imap based (quotas, acl's).

This should be customizable.  By default we stick with the sasl/sasl2 interface
and have a config option to let the user say we want to use ldap, mysql, whatever.

I guess I'm thinking of:

userBackend = 'sasl2';  // sasl, sasl2, ldap


- ---


We should probably install /etc/mailadmin/settings.{php,pl} config files that
get included by the config.inc file or the perl scripts (assuming we still need
them) and thus let the perl scripts be able to get the backend to use (sasl,
sasl2, etc.), the admin username and password, and imap seperator without us
having to pass them in on the command line.

By having a global /etc/mailadmin/settings.{php,pl} file, we can have an install
script that asks the user what the database name is, user to use, etc., populate
the config file snippet and create the database and have our
/usr/share/mailadmin/includes/config.inc file just source that file.  All the
critical user changes would be in /etc/mailadmin/settings.{php,pl} which will
get around some of the limitations that different distros have in having a
config file in /usr.  (Debian comes to mind)

That should help upgrading to be much easier.

- --
James A. Pattie
ja...@pc...

Linux -- SysAdmin / Programmer
Xperience, Inc.
http://www.pcxperience.com/
http://www.xperienceinc.com/
http://www.pcxperience.org/

GPG Key Available at http://www.pcxperience.com/gpgkeys/james.html
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFAakY8tUXjwPIRLVERAqyMAJwLuUBkxDmxxT7hnO/iB2e6Zpc4TwCgmnye
XHSl7SSs+S7fL6L5V8AwY58=
=4brK
-----END PGP SIGNATURE-----

-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
MailScanner thanks transtec Computers for their support.