Dominic Amann wrote:
I am currently running dbmail-mysql version 1.2.11-1, with dbmail-imapd
and postfix on a production server. I am debating whether to upgrade to
2.0.3, and I would need a few questions answered to make this decision:
1. Is 2.0.3 stable (compared to 1.2.11)?
I should bloody well hope so :-) But time alone can tell.
2. Is migration straightforward (on debian sarge)?
Pretty much so. Since you use the debian packages already, you should use my debian packages on
debian.nfgd.net. All the config stuff like db-connection will be preserved, even when you select 'use
maintainers version' when offered a choice about dbmail.conf. This may reset some values for trace_level and
so, but will also add the lmtp section which is required stuff if you intent to use lmtp.
The sore spot about moving from 1.2 to 2.0 is the database. There is a thoroughly tested migration sql script
included in /usr/share/doc/dbmail-mysql/examples. This upgrade hasn't been automated yet, which is one of the
main reasons I haven't uploaded dbmail-2 to master yet (the other main reason was stability; only now with
dbmail-2.0.2 and 2.0.3 have we ironed out some really annoying bugs).
Basically, make sure you backup your dbmail-1.2 database, stop your mta just to be sure, upgrade to
dbmail-mysql_2.0.3-0.20050112, run the migrate_from_1.x_to_2.x_innodb.mysql script (if you're not running
innodb, move to innodb tables first!), and start dbmail.
In fact upgrading is pretty safe: the daemon's won't start until after the migration script was run, nor will
any of dbmail's tools. So even if you don't stop your mta, no mail should be lost.
3. Will it perform better?
Oh yeah, much faster in many cases.
--
________________________________________________________________
Paul Stevens mailto:[EMAIL PROTECTED]
NET FACILITIES GROUP PGP: finger [EMAIL PROTECTED]
The Netherlands________________________________http://www.nfg.nl
