There are a couple more I'd like to see. For logging, I think a really
complete set of options should be in the config file. It is critical that if
the database cannot be contacted, that the errors are logged to the right place.
For the database settings, I've started to look into dl() and dynamically
loading our database abstraction at run-time. So when we get to coding that,
we'll need a dbtype={mysql,pgsql,...} option.
For authentication, I'm not sure if it should be in the config file or in the
database. On the one hand, you don't need the auth info immediately, and do
need to be in contact with the database for the auth info to be relevant
anyways, so it could be in the database. On the other hand, if you have LDAP
passwords it might be safer to keep them in a file.
I'm leaning towards auth info in the database, because I'd like to see the
config file be as short as is possible, and because a profile/hostname of '*'
would allow me to really easily add mail hosts and keep the auth information
synchronized. For example if there's an LDAP change and 20 hosts need to be
updated... ugh.
Aaron
Brian Blood <[EMAIL PROTECTED]> said:
> IMNSHO, the dbmail.conf file should have ONLY these 7 config options:
>
> # Database settings
> host=127.0.0.1
> user=dbmail
> pass=password
> db=dbmail
> configtable=dbmail_config
> configprofile=PROFILE1
> TRACE_LEVEL=2
>
>
> EVERY other config option should be in the config table specified keyed
> under the profile specified.
>
> and there should be a dbmailctl program which you can call like the
> following:
>
> dbmailctl start
> dbmailctl stop
> dbmailctl reload
>
>
> This is just my opinion of course.
>
>
>
>
>
> Brian
>
> _______________________________________________
> Dbmail-dev mailing list
> [email protected]
> http://twister.fastxs.net/mailman/listinfo/dbmail-dev
>
--
