Been reading up on DBMail after someone recommended it to me, but, I
have a question regarding the storing of emails, with respect to
efficiency...
I did search the archives and read through most of the docs, and saw
something mentioned about a Feature Request for separating out the body,
headers, attachments, etc, but nothing specifically about the issue I'm
interested in...
Our business model (advertising industry) is such that our users
exchange a lot of emails with attachments - most less than a megabyte,
but some considerably larger. Consequently, I have been looking for a
good, open source imap server that doesn't store multiple copies of the
same attachment - but instead, stores a checksum (or some other way to
fingerprint it), and whenever a message is stored with a duplicate
attachment, the attachment is stored only once, and simply referenced by
some kind of link to other emails.
This would *drastically* reduce the storage requirements for our company
- imagine a message with a 10MB attachment, sent to 40 of our users,
sometimes more than once. Now multiply this by 10 users, 3 times per
day, for 5 years...
Are there any plans for DBMail to support this type of storage in the
future? It seems to me that since DBMail uses an SQL database as a
backend, it is ideally suited for something like this.
--
Best regards,
Charles
