Excluding attachments when producing native emails

Table of Contents

Generally, Everlaw prevents the parent documents of any redacted or withheld children from being produced in native, as well as the parents of documents that are not included in the production. This is true even in cases where a family member is in the database, but not the project. Instead, only the image and text formats of the parent documents, if available, will be produced. Enabling the Project Settings option to “Exclude attachments when producing native emails” allows you to produce native emails even when one or more attachments is redacted, withheld, or excluded from the production.

Project Settings

Project admins have the option to exclude all attachments of emails when producing any native emails. Enabling this setting can be one way to exclude inadvertent attachments from your production when producing native emails.

By default, projects will have the “Exclude attachments” option disabled. A project admin can enable this setting by navigating to Project Settings and then the Production Tools section of the General tab. All protocols will be updated to reflect the current status of the setting, but past productions will not be affected.

final.png

Return to Table of Contents

Productions

When project admins enable the option to exclude attachments when producing native emails, all native email files will not include any attachments, including grandchildren. If documents that are attachments are included in the production set, they will be produced and families will be grouped together.  

Note: all native emails with attachments will be produced as standard EML files, regardless of their original extension. 

Document family examples

The following examples illustrate the differences between produced families with natives when the “Exclude attachments” toggle is disabled or enabled. 

4.png

  • One grandparent email, one parent non-email, and one redacted child document are included in the production set. 
    • When “Exclude attachments” is disabled, the grandparent and parent natives will never be produced. 
    • When enabled, the native email grandparent can be produced with its attachments removed and the non-email parent and redacted child will not be produced in native.

5.png

  • One grandparent email and one parent non-email in the production set have a withheld descendent.
    • When “Exclude attachments” is disabled, the grandparent and parent natives will never be produced. 
    • When enabled, the native email grandparent can be produced with its attachments removed and the non-email parent and withheld child will not be produced in native.

6.png

  • One grandparent email and one parent non-email have a descendent that was not included in the production set. 
    • When “Exclude attachments” is disabled, the grandparent and parent natives will never be produced. 
    • When enabled, the native email grandparent can be produced with its attachments removed and the non-email parent will not be produced in native.

Add_a_subheading.png

  • One grandparent email has an email descendent that is not included in the production set and that descendent has a child document that is included in the production set. 
    • When “Exclude attachments” is disabled, the grandparent native will never be produced. 
    • When enabled, the native email grandparent can be produced with its attachments removed so the parent's native will not be inadvertently produced in native, and the child document can also be produced in native. 

Return to Table of Contents

Have more questions? Submit a request

0 Comments

Please sign in to leave a comment.