Hello, We're working on a multi-server setup with a single database server, and multiple postfix/dbmail servers connecting to it. It seems the current (database-stored) configuration setup (ie. config table) does not handle this, as most of the settings may/will be server-specific. The most prominant example would be POP3D_BIND_IP and IMAPD_BIND_IP, which if not '*' will be different on every machine, but most all the variables really should be server-specific.
I'm pretty sure I can get around this by setting up nearly identical machines (including user/group names, etc.), and bind to '*', so it's not a "showstopper" problem, but is there a way to handle this currently, or is this something that needs addressed? If the latter, a few thoughts on the design - there does need to be one central config source for the entire system, that each dbmail server will consult (ie. in the database), and then a way to have server-specific values. One way would be to have server-specific values saved in a local config file (eg. dbmail.conf) - alternately could add a field to the config table to specify which server the config setting applies to (global if empty, otherwise it matches the server's hostname or ip addr). Or, did I just miss something in how I have this setup? Thanks, Jesse -- Jesse Norell [EMAIL PROTECTED]
