Processing Container Files (ZIP, RAR, CAB)

Container files (ZIP, RAR, CAB, PST) can appear at various levels of the file population and are treated differently depending on where they are located. See Processing Email Files for information on processing PST, NSF, MBOX files.

Containers Used to Deliver Files

For Automated delivery, the files must be delivered in a ZIP or RAR container to minimize file size and for ease of transfer. When these files are exploded, the original container is not included as output.

Container Files Included Among Loose Files

Container files discovered in loose files delivered to Catalyst will be processed as a top-level file and exploded into their individual components. We create a placeholder PDF page for the container file and include information to alert the user that the file is a container and not suitable for viewing.

If the container file contains further container files, they will also be exploded into individual components and treated in a similar fashion. This process will continue recursively until complete.

Container Files Found as Email Attachments

Container files found as attachments are exploded. We create a PDF page for the container file itself to alert the user that the file is a container and not suitable for viewing. Container contents are exploded separately and recursively until the items are not divisible. They will be treated as related documents to the parent email.

If an email store is found attached to an email, it is processed as a top-level file and the relationship to the parent file is severed.

Process PDF Portfolio Files as Containers

We process PDF portfolio files as container objects and extract the individual files as children of the portfolio.

Other Containers Requiring Special Treatment

Certain container files require special treatment (custom conversion or manipulation) to process. We convert unsupported container types to supported container types, for example OST to PST, prior to processing. These include:

Catalyst will confer with you to determine your preferences for handling custom processing. There is an extra charge for this service. Contact us for any other custom container file handling.

Containers with Password Protection

If a container file is password protected or otherwise inaccessible, it will be included in an exception report. We will then seek further instructions from you.

Per your instructions, we can attempt to open these files using password cracking software. There is an extra charge for this service. We can also send them to a forensics company.

Flattening the Container Hierarchy

Container files and their attachments can extend many levels (e.g., a ZIP has an attached message, which has an attached ZIP file which contains more messages). Catalyst only creates a one-level hierarchy. Thus, no matter how many levels the attachments and their progeny extend, Catalyst only shows two levels: the parent and all attachments to that parent.

When a ZIP is attached to an email, the parent would show a large number of attachments: the ZIP would be related to the message and the further attachments to the message. All of these files would show as related to the single parent file.

Email containers constitute an exception to this rule. Email containers (PST or NSF), wherever located, are removed from the hierarchy and processed as separate jobs. A placeholder is added to the original parent to show the existence of the email container. See Processing Email Files for more information.