Thanks for the comments guys - replies below... On 2012-02-09 3:16 AM, Grayhat <[email protected]> wrote: >> Charles - this could be done with the ASSP_AFC plugin in V2. Without >> the plugin a mail with a bad attachment is blocked - the plugin will >> replace the bad attachments with a text part. >> Including a download-link to a replaced bad attachment seems not to >> be wise.
Agree, see below... >> Or do you mean a feature like DAOS in Lotus Domino ? In case, IMHO >> the local mail server could do that better, especially in a multi >> domain environment. > Hmm... I suspect that Charles was thinking to something similar to > "DAOS", yes ... Yes, precisely... As to Thomas' comment, I absolutely agree - but this feature should only then apply to attachments that are *not* considered bad by ASSP... So, were this to be implemented, if ASSP detects the attachment as 'bad', it works as it does now... but if it doesn't, then it forks to this new feature/process to strip the 'good' attachment and replace it with a link. > as for the feasibility ... well, it /may/ be done inside the AFC > plugin; <snip> excellent description of how it could work > this way, multiple files with the *same* content won't take up more > space since they'll be saved just once :) This is exactly what I am interested in, and why. Basic testing on my mailstore reveals that about 85% of the mail store is attachments, and 40-60% of that amount could be eliminated by deduplicating just the attachments. I've been considering hiring someone to implement this server-side using MIMEDEFANG, but like I said, thought I had remembered seeing this discussed here a long time ago and didn't know if this was ever implemented. > - sure, the admins should then take care of cleaning up the storage > folder from time to time (this is NOT a task for ASSP) but that may > be viable imHo; Personally, since there will never be duplicate attachments, keeping them forever (or at least for many years) shouldn't be a real problem, and that is what I would do. The simplest way for those who don't want to store them forever would be a simple time limit - in the link/text the attachment is replaced with, inform the user that that attachment will be deleted in XXX days, so if they want a permanent copy, download it locally and store it somewhere they control. Then all you need is a simple script that deletes based on file age. > the only real problem I see is that ASSP should do more work since it > will need to strip and save the attachments so, I'm not sure it may > be ok for "busy" systems Maybe this process could be moved to a separate worker thread with a lower process priority, so that other mails would not be impacted so much... The biggest problem that I see for someone like me is what to do about *existing* mailstores. Whatwe would also need is a script that runs against an existing mailstore that rips out the attachments (creating the MD5SUM), replaces them with the link/linktext and uploads the attachment to the defined location. Most likely the best thing to do for this would be to provide a few sample/example scripts for the most popular imap servers (dovecot, courier-imap and cyrus maybe - I'm fairly sure Microsoft Exchange already has this capability natively), and leave the precise implementation to the sysadmin, along with appropriate scary warnings about potential data loss if they make a mistake. -- Best regards, Charles ------------------------------------------------------------------------------ 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
