You are here:

E-Mail Backups

Introduction

Incoming e-mails which could not be processed are stored in a special store in the CM system (the location varies depending on the mode of the incoming mail configuration, see ESB and NIMH sections below).

You as an administrator can then try to re-send the e-mails to the system manually. The e-mails stored here can also be deleted, e.g., spam e-mails.

IMPORTANT INFORMATION

Since ConSol CM version 6.9.4, there are two modes to receive incoming e-mails:

Mule/ESB - this has also been available in all previous CM versions
NIMH (New Incoming Mail Handler) - new in version 6.9.4

For all configurations/settings which are valid for both modes, no further notes are added. For all settings which vary depending on the mode, this will be explained in separate (i.e., Mule/ESB- or NIMH-specific) sections.

E-Mail Backups in the Admin Tool

All e-mails which could not be processed are listed in the navigation item E-mail Backups in the navigation group E-Mail. If your system is running in Mule/ESB Mail mode, the Mule/ESB backup e-mails are displayed, if the system is running in NIMH mode, the NIMH backup e-mails are displayed. Backups of both types are never displayed at the same time!

Usually, when an e-mail cannot be processed, this is caused by one of the following reasons:

One of the e-mail scripts (see section Scripts of Type E-Mail) has a bug and therefore the e-mail which has been fetched from the mail server cannot be processed further in CM.
The attachment of the e-mail is too large. For NIMH, the size limit is defined by the system property cmas-nimh, mailbox.default.task.max.message.size or by a mailbox-specific value, e.g., cmas-nimh, mailbox.1.task.max.message.size.

Figure 377: ConSol CM Admin Tool - E-mail: E-mail backups

The list panel for unparsable e-mails contains the following elements:

File name
This field provides a filter. When you enter the name or part of the name of e-mail files, only the matching file names will be displayed in the list.
Name
The name of the e-mail file (usually with an .eml extension).
Date modified
The last date when the file was modified. Usually the date when the e-mail was stored on the ConSol CM server.

In an error-free ConSol CM system, the list panel for unparsable e-mails should be empty. If there are e-mails listed, an error has occurred in the processing of those incoming e-mails. Please see section Scripts of Type E-Mail for a detailed explanation of the processing pipeline.

You can perform the following actions with e-mail backups:

Delete
To delete an e-mail from the list, select the list entry and click Delete. Please keep in mind that the information will be lost! It will not be saved or transferred to ConSol CM in any way!
Re-Send (Import)
You can also re-send (import) the e-mail to the processing pipeline (e.g., when a script was not working correctly and has been fixed) by selecting it in the list and by clicking Resend.
Export to file system
You can export an e-mail as .eml file to the file system of the machine where the Admin Tool is running (e.g., for further analysis of an error-prone e-mail).

Management of E-Mail Backups with Mule/ESB

Incoming e-mails which could not be processed are stored in the file system, in the following directory (as .eml files):

<CMAS_DATADIR>/mail/unparsable

This is done when the system property cmas-esb-mail, mail.db.archive is set to true. If this property is set to false, no e-mail backups are saved.

E-Mails which are stored in the unparsable directory and get re-sent successfully are transferred from the unparsable directory to the following directory (as .eml file):

<CMAS_DATADIR>/mail/reimported

Management of E-Mail Backups with NIMH

Incoming e-mails which could not be processed are stored in the ConSol CM database, in the following table (as .eml files):

cmas_nimh_archived_mail

The system behavior concerning e-mail backups with NIMH is controlled by the system property cmas-nimh-extension, mail.db.archive.

If the property is set to true, all incoming e-mails are archived in the database. If the property is set to false, the e-mails which can be processed are deleted after processing. The e-mails which cannot be processed will be stored in the database as long as they have neither been processed nor deleted (which can be achieved by reprocessing or deleting such e-mails, see section above). An e-mail database entry will be deleted automatically after being successfully processed.