> And of course, the other advantage is (assuming this feature would work > when sending messages too), people could send messages with large > attachments without worrying about whether the recipient could receive > it or not - like a seamless way to do the same thing that services like > sendthisfile.com or yousendit.com do. > > Oh - and for internal messages to multiple recipients or for locally > hosted mail lists (ie, mailman), the attachment only has to be processed > once, instead of once for each recipient... so, in many cases, the load > on ASSP would actually be *reduced*...
I have haven´t really followed this discussion all the way, but there is a open source mailstorage that does support single instance storage for attachments: dbmail. iirc it supports that since 2.3 and current version is 3.0. It does that transparently, so there are no links in the email to replace the attachment/mime part, you just see the email without any changes. On the backend the mime parts all get a hash, and mime parts which are the same, are stored only once. Greetings, Daniel ------------------------------------------------------------------------------ Virtualization & Cloud Management Using Capacity Planning Cloud computing makes use of virtualization - but cloud computing also focuses on allowing computing to be delivered as a service. http://www.accelacomm.com/jaw/sfnl/114/51521223/ _______________________________________________ Assp-test mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/assp-test
