On 2013-08-29 10:42, Reindl Harald wrote:
Am 29.08.2013 09:35, schrieb Iaan Louw:
I run dbmail together with postgres on ubuntu.
I recently ran:
dbmail-util -actbpdsMy
Where the -M denotes: migrate legacy 2.2.x messageblks to mimeparts
table. in the man file.
It was working fine before I converted the messages, would anyone
perhaps just satisfy my curiosity on WHY this
should be done, I have googled but no one really mentions what the
differences and advantages is between 2.2.x and
whatever the new version is? Or is it just a case that the old format
will be stopped being supported?
because dbmail >= 3.0 does mime-parts-deduplication what saves *a lot*
of space
in case of CC/BCC messages with attachments and such things
"stopped being supported" maybe not directly but handeled with less
care over the
time, i am *not the* developer, but i am developer and so i make a
good guess :-)
There actually is an explaination in the UPGRADING file:
http://git.dbmail.eu/paul/dbmail/tree/UPGRADING?h=master
....
Schema Changes
Migration scripts from the previous stable releases are provided in
sql/mysql, sql/postgresql and sql/sqlite. Please test them first
before applying them to your live database. Especially people who have
modified their tables, and users using databases that go back to 2.0
or earlier should take special care.
The schema for 3.0 adds new tables for single-instance storage of
mimeparts, and for supporting user labels on messages in IMAP.
Migration of old data is supported through dbmail-util, but until
you migrate the old data will remain accessible. New messages will
be stored in the new schema.
Also, the header caching tables have been revised. This means they
will have to be dropped, re-created, and re-filled using:
dbmail-util -by
....
_______________________________________________
DBmail mailing list
[email protected]
http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail
