Q. What are the pros and cons and other considerations of native production in the MSG format?
- An .MSG is the native file format for Outlook message files. One MSG file
equals one message in outlook with its associated content (i.e. attachments);
- This production is allowed, but one can choose to argue if the agreed upon format was TIFF, which may turn out to be another court battle.
- Inclusion of email metadata, headers, etc.
- There is no need to convert to TIF and OCR. Just be careful with attachments, however, as they may be encoded and not directly searchable without prior extraction;
- Attachments and embedded files are seen as the person who created or used would have seen;
- Ability to inspect email threads, verify time zones, make sure one sees actual email addresses rather than just the names displayed in a print job, get all the names and not just the ones that made it to the print job, have a generally more reliable access to attachments;
- Since emails are not in an "e-paper" format like TIF, review may require additional production effort (such as "early assessment" technology products), adding Bates numbers, etc.;
- Emails may come in unsorted folders;
- The production may not have been QC'd;
- MSG production may include data that was not intended for production. For example, the parent email was responsive, but the attachments were not;
- Redactions will not appear on the MSG files;
- By providing information in MSG format, the associated metadata with
the files may not be preserved;
- Attorneys can review documents faster when they are in image form as opposed to native further increasing costs to the client;