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

[Chris B. <ch...@hu...>]

At 12:17 AM 3/31/04, James A. Pattie wrote:
>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).

k, we just need to make sure we have various options enabled to be able to 
do that...

>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

This would help manage it :>


>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.

That works, sounds cool..

>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.

agreed.