h.reindl at thelounge
Mar 7, 2012, 4:33 PM
Post #2 of 3
Am 07.03.2012 07:48, schrieb nuar deniel:
> We are currently using DBMail 2.2.10, and planning to upgrade it 3.0.
do NOT use 3.0
3.0.1 is out fixing a lot of bugs
@Paul - seems you missee to refresh http://www.dbmail.org/
after the announcement on the list!
> The steps to upgrade is as follows:
> 1. Install DBMail 3.0 in a new server
and make a backup before you start
really do not forget!
> 2. Run the sql/mysql/2_2-3_0.mysql in the production SQL Server
first edit the "dbmail.conf"
i would strongly recommedn a planned downtime of mailservices
if you are having POP3 clients with slow connections i would
recommend high timeouts, Outlook 2003 was kickend on our setup
after some minutes - there is a bugreport and confirmation
somewhere in the list-archive, i guess not easy to debug because
it affected only Outllok 2003 AFAIk and not 2007
.... other settings .....
timeout = 1800
login_timeout = 1800
> 3. Edit the my.cnf file
in which way?
the mysql-configuration stays the same
dbmail is the component with hughe changes
> 4. Voila, DONE.
> Is that all? Or am I missing anything?
yes: "dbmail-util -by" or your users are not happy
missing subjects in the list view of their client
i can remember
>> Oh boy,
>> UPGRADING clearly states you need to run
>> dbmail-util -by
>> to refill the headercache tables
>> But perhaps not clearly enough...
from Paul after my whining on the first test machine
because the line is somewhere between important infos
and the logging stuff in the UPGRADE file and i missed
it completly :-)
i wrote some scripts and a optimized convert-sql
while/after preparing our main server, however
i would recommend to clone the database somewhere
and make a cold run to fix any duplicate-key issues
before run a upgrade on production servers
this thing is well docuementaded and can currently not used without
modifications on moster servers, but it is based on a pre 3.0.1
snapshot and did the migration of around 66.000 messages well
the nightmare after the migration was some days of hard debugging
work with Paul and should be mostly cleaned up in 3.0.1
personally i would recommend http://git.dbmail.eu/paul/dbmail/commit/?id=624b5df6ea31f4b6957e50c32a075de088dc51a5
since it fikes an additional memory leak (there are currently also some
but the most terriblle are fixed leading to really hughe memory
usage after a short time with many clients)
if you are not in hurry maybe you should wait for 3.0.2
there are some nice fixes after 3.0.1, one not finally fixed
issue with thunderbird and folder-subscription, but yes 3.0.1
as really fine at all, but not perfect if you expect this
we are currently running the latest snapshot
which mitigates the subscription problem (unsubscribed folders doe snot
disappear, but can not be used and not subscribed again) in a way
the unsubscribe is ignored completly, i guess this will be fixed soon
but i should NOT recommend using snapshots to anybody except mysqlf