Paul J Stevens wrote:
Jesse Norell wrote:
Does the 2.2 imapd handle missing header caches (and eg. dynamically
look up the message and fill the cache)? If not, that would be a
substantial problem, though pop3 would probably work fine, afaik.
No. There's no graceful degradation in the imap behaviour. The new
tables are *required* for correct imap behaviour.
If you want maximum uptime:
1. install 2.2 on hostB while keeping 2.0 up and running on hostA, Both
connect to the same DBMS instance.
2. add the new tables (don't do the BYTEA conversion yet)
3. run dbmail-util -by on hostB so the new tables are filled.
4. run the BYTEA conversion on the messageblks table.
5. move the mailrelated ip addresses from hostA to hostB.
Only during steps 4 and 5 will users experience downtime because of the
tables locks. Also, you will probably want to stop your MTA from
inserting new messages during this procedure.
Interesting. One comment though, why do these need to be on different
hosts? You can run the old and the new on the same host if you are a
bit careful. What I do it ./configure --prefix=/some/place and then
before I compile I edit dbmail.h and set paths for dbmail.conf, the pid
file and the log files that are all under my configure prefix. That way
DBMail only look for files under my configure prefix and I won't have
any problems running different version of the software on the same host.
At some point I would really like to see DBMail honor the configure
prefix more strictly, that is, I would like it to set the file paths in
dbmail.h and dbmail.conf to have the configure prefix in them.
