On Tue, 29 Nov 2005, M. J. [Mike] OBrien wrote:
1) Yes to DBMail 2.07 (not 2.x for production!!!) 2) Yes to InnoDB (for sure)
My question/issue/source of discomfort is the move from MyISAM to InnoDB. Is there a quick/easy HOW-TO on this? I read through the docs on Mysql's website, but just don't feel comfortable doing it without someone "watching", to give me a hand to hold onto if needed.
3) http://www.dbma.ca DBMailAdministrator replaces all your PHP user management/
The PHP involves much more than just dbmail. It is my provisioning system for new users, my ticket tracking mechanism, my radius provisioning system, etc. I have looked at DBMA, but it is not going to do all that I need to do.
4) Don't mess with the running system. Consider building a parallel system; migrating your existing accounts and mail and then when fully satisfied, roll out the new system. You need to time the events so that you can at the time of final mail migration, freeze the database against writes while the MTA stores/queues mail. As you failover to the new system, you push out the new database into production; and have the MTA flush and forward then resume normal mail via dbmail-lmtp / dbmail-smtp (whatever transports you use) to the new DBMail 2.0.7 system.
This is a good idea. I will certainly do it this way.
5) Make it easier... Why not have everything on the same server? Is your MTA really that busy? You can then use your other for WebMail, Admin, MX2 etc.
Well, it's the way it is, because my virus/spam scanning happens on the machine that handles the smtp as well as (currently) the dbmail daemons. This machine is an older machine, and the combination of a busy mysql server (there are other things using the mysql server) and the spam/virus scanning is pretty CPU intensive.
-- Butch Evans BPS Networks http://www.bpsnetworks.com/ Bernie, MO Mikrotik Certified Consultant (http://www.mikrotik.com/consultants.html)
