Josh Berkus wrote: > Keen! Hopefully I'll be able to do a write up on replicated e-mail with > dbmail ...
On postgresql perhaps? > > Where do attachments go? Depends. In 2.2 everything is chopped up into 500k blocks and stuffed in blobs that are simply concatened on retrieval. So attachments are not saved separately. Headers are stored in normalized tables. In 2.3+ attachments are indeed stored as atomic blobs in the mimeparts table. The rfc822 header part of the complete message, and the headerpart of attached mimeparts is also stored as blob in the mimeparts table. Mimeparts are linked into actual messages by the partlists table. Retrieval put the right blobs in the right order and depth, separated by the correct boundary. if you want to look at the storage behaviour of 2.3+ you can use 2.3.2 or 2.3.3 without worrying too much about losing email. I use 2.3.2 on one key inhouse production system that carries around 25GB storage and around 10 heavy users. Zero complaints. 2.3.3 has a lot of new and relatively untested code with known issues and very likely some unknowns as well. Of course I'm personally very excited about all the new stuff which I think will help solve some fundamental issues. But I'm also sometimes a bit overwhelmed with the tasks still before me. Behind every hill, lies another one, so to speak. More to the point: it looks like I have to rewrite the whole mime parser from scratch. GMime is not threadsafe, and adding mutex locks appears to completely kill performance. But then again, things may be not quite that bad after all. I havent figured it out quite yet. Which makes it just one of those things: they take time to work themselves out. -- ________________________________________________________________ Paul Stevens paul at nfg.nl NET FACILITIES GROUP GPG/PGP: 1024D/11F8CD31 The Netherlands________________________________http://www.nfg.nl _______________________________________________ DBmail mailing list [email protected] https://mailman.fastxs.nl/mailman/listinfo/dbmail
