Boston Linux & Unix (BLU) Home | Calendar | Mail Lists | List Archives | Desktop SIG | Hardware Hacking SIG
Wiki | Flickr | PicasaWeb | Video | Maps & Directions | Installfests | Keysignings
Linux Cafe | Meeting Notes | Blog | Linux Links | Bling | About BLU

BLU Discuss list archive


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

E-discovery best practices?



On 1/25/07, Kristian Hermansen <kristian.hermansen at gmail.com> wrote:
> On 1/25/07, John Abreau <jabr at gapps.blu.org> wrote:
> > My boss wants me to come up with a plan for preserving
> > email in accordance with that new law that took effect Dec 1.
> > I've been poking around through google to see what others
> > are doing, but I haven't come up with anything useful yet.
>
> Does this help?
> http://www.doculogix.com/doculogix/index.asp
> --
> Kristian Hermansen

Not really. That looks to me like something to analyze the archives
you've already
kept by some unspecified procedure, once you're being sued. I'm
looking for advice
on deciding what to preserve and how best to preserve it, which appears to be
outside the scope of what that site talks about. I found plenty of
links to sites
like that.

I could just mirror everyone's Maildir directories and ensure that nothing
ever gets deleted; but files would get duplicated as people refile messages
to different folders. And don't Maildir message files encode metadata in
the filename, for things like Unread or Deleted status? That would mean
more redundant copies. I could roll my own scripts to analyze the Maildirs
and try to avoid saving multiple copies of each message.

But this is exactly the sort of ad-hoc kludge I'm trying to avoid. What I'm
looking for is a decent description of Best Practices in this area.

-- 
John Abreau / Executive Director, Boston Linux & Unix
GnuPG KeyID: 0xD5C7B5D9 / Email: abreauj at gmail.com
GnuPG FP: 72 FB 39 4F 3C 3B D6 5B E0 C8 5A 6E F1 2C BE 99

-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.





BLU is a member of BostonUserGroups
BLU is a member of BostonUserGroups
We also thank MIT for the use of their facilities.

Valid HTML 4.01! Valid CSS!



Boston Linux & Unix / webmaster@blu.org