In his keynote at INTERACT2008, Terry Myerson will be addressing some of the top questions and issues that we hear from customers around Exchange Server 2007. If you could ask Terry anything, what...
Updated Jul 01, 2019
Version 2.0
Blog Post
I think the Exchange model for handling Messages/Attachments/Single Instance Storage (SIS) has reached its limits.
I think Messages should be stored in one place -- and Attachments stored someplace else other than the Mailbox Stores. (Attachments should be stored in a database or a file-system share or a Sharepoint library, if that scales sufficiently.)
In this way, the moment a message is received from an outside party, or a message is generated internally, the attachment would stored in a SIS within the organization. Ideally you would like to see MIME still work as-expected, so that when the message is sent from internal to external, the attachment goes along for the ride.
Our company uses a third-party archiving package -- but it really would be unneccessary if Exchange handled Single-Instance-Storage of attachments, efficiently from the moment the mail is generated.
I think Messages should be stored in one place -- and Attachments stored someplace else other than the Mailbox Stores. (Attachments should be stored in a database or a file-system share or a Sharepoint library, if that scales sufficiently.)
In this way, the moment a message is received from an outside party, or a message is generated internally, the attachment would stored in a SIS within the organization. Ideally you would like to see MIME still work as-expected, so that when the message is sent from internal to external, the attachment goes along for the ride.
Our company uses a third-party archiving package -- but it really would be unneccessary if Exchange handled Single-Instance-Storage of attachments, efficiently from the moment the mail is generated.