In my forthcoming guideline to email preservation, I make the point that far too many email ‘preservation’ systems or policy guidelines ask too much of users. Who is going to read, much less understand-, a five page or more email policy document. And if they do, will users really make appropriate decisions about which particular messages to classify as ‘record’ or ‘non-record’ items (assuming they can even understand the distinction)?
To that end, I was refreshed to read this good advice in the New York Times. I really like the techniques it suggests for overcoming email overload, since they really mesh will with a medium term ‘do nothing’ preservation strategy–provided you keep messages on the server and have access to a more or less unlimited amount of server storage, and can come up with a way to migrate or capture messages at a later time, using either email migration software or an email archiving application.
If I have time later, I’ll expand a bit on some of the ideas laid out in this article.