Paul J Stevens wrote: > Karl wrote: >> Hi, >> >> I'm new to dbmail and this list. I apologize if this has been >> asked before but I couldn't find an answer to these questions >> in the wiki & list archives so far ... >> >> 1. is there a way of doing a single instance store for ATTACHMENTS? >> The reason behind this is: most of the time larger eMails are >> large because of their attachments, not becuase of the textual >> eMail body. So having a single-instance store for eMails doesn't >> save that much, however, if there would be a single instance >> store for ATTACHMENTS (eg. by size/md5) that would save a LOT of >> space ... just think about all the people receiving some photos >> and videos by mail and then forward it to others - that causes >> a new mail, but same attachments ... > > The master tree (2.3.x) does just that: single-instance storage for all > mime-parts in the messages.
Thanks Paul, is it done by md5 or what method is used to identify a single instance? Can you point me to the right place for documentation please? >> 2. is there a way to store attachments (and/or email bodies) as >> FILES on disk rather than in the database? This would not require >> any packet size tuning to the database and keep the database slim, >> containing the header information only ... > > No. > >> - for those who have done any coding on this project - >> >> 3. is there a single place (abstraction) where objects are stored >> into and retrieved from the database? If yes, it would be easy to >> add the functionaility mentioned above and I'd be interested in >> looking into it ... > > src/dbmail-message.c holds all the keys to message storage and > retrieval. But like I said, single-instance storage is already a done > deal. Storage on the filesystem is not gonna happen since it defeats the > purpose and design of dbmail. If you need filesystem storage there are > other imap servers to look into. Well, that's right, there's lots of other imap servers that do maildir etc. BUT I like the fact of having all meta-information about the mail in SQL (from, to, date, subject, msgid and perhaps even the (part of the) mail body as long as it's txt (text/plain or text/html), while I'd rather store binary attachments (mostly pictures, videos, other external documents) as files since IMHO I don't see any point in storing them in the database - it just grows it huge ... For me the primary argument for a database is it's searchable and sortable but that doesn't apply to the (binary) mime parts ... Am I thinking in the wrong direction? - Karl _______________________________________________ DBmail mailing list [email protected] http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail
