Email Processing

WIP	This article is a work-in-progress or created as a placeholder for testing purposes. This article is subject to change and/or expansion. It may be incomplete, inaccurate, or stop abruptly. This tag will be removed upon draft completion.

This article seeks to provide guidance for users processing documents coming from an email inbox. Grooper can ingest email messages, condition them for further processing, and process the email's body and/or any attachments (just like any document in Grooper).

However, there are several considerations when processing documents that come in from an email source.

1. Import considerations - Are you importing emails manually or do you want an Import Watcher service to periodically poll an import source for new emails coming in or bring them in at scheduled times?
2. Attachment considerations - Does the email have attachments that need to be processed?
3. Body considerations - Do you want to process the email body? If so, do you need to just process the body's text? Do you need to process the rendered HTML seen in an email client? Does the email have any images you need to process?
4. Conditioning considerations - Based on your answers to questions 2 and 3, the Batch Process will need to be adjusted to accommodate the scenario.
   • This article will step through a Batch Process that accommodates all common scenarios. This will give you a starting point to process email content, normalizing source content for further processing.

Import considerations

When importing emails, you should use one of the two CMIS Import providers. Either Import Descendants or Import Query Results.

Of the two, Import Query Results is more common for importing email messages. This article will focus on using this provider.

Main import considerations When configuring email import, there are three main considerations:

• How do you want to connect to the email source? Grooper will use a "CMIS Connection" to do this.
• Do you want to perform a user-directed (ad-hoc) import?
• Do you want to perform automated (polled or scheduled) imports?

Common secondary considerations After answering these questions, there are other considerations you should evaluate.

• Are you going to filter the import by properties like the sender or sent date or text in the subject line?
• Particularly important for automated imports, how are you going to dispose of the emails after importing them?

Creating a CMIS Connection

To use Import Query Results you will first need a CMIS Connection. A CMIS Connection is what Grooper uses to connect to external content management systems, including email clients. There are two "CMIS Connection Types" that can be used for email imports.

• Exchange - Connects Grooper to email
• IMAP