> If we migrate everything over to the new release, will the existing > messages be checked for duplicate mimes/attachments and take advantage > of the “single instance storage?” Basically, will the existing > duplicate mimes which were stored as separate copies be removed and > only one copy is stored?
It was mentioned previously that an existing database will still work, but new messages will be inserted in the new format, so if you merely upgrade your schema/programs, I think the answer is no. If by "migrate" you use imapsync or something, it would depend on if imap stores in the new format or not (and I can't answer that). A nice feature (which I think has been mentioned in one form or another in the past) would be a mode of dbmail-util that would run in the background to do the conversion. Eg. convert X number of messages, then sleep Y seconds, until they're all done (or use something smarter than "sleep Y seconds" to do more work when there's less load). If the bulk of a message conversion could happen at the messageblks/mimeparts level first, then changing the underlying message entry to point from blocks to parts (which would require a transaction/lock) should be pretty quick (though I've not looked at the new schema). -- Jesse Norell Kentec Communications, Inc. [EMAIL PROTECTED] _______________________________________________ DBmail mailing list [email protected] https://mailman.fastxs.nl/mailman/listinfo/dbmail
