› Importing documents › Email Import configuration › Multi-server email import

Multi-server email import

The optimal Transact email import configuration is to run email import on one server in a multiserver environment. However, if you do configure email import on multiple servers, it is best to have them check every 10 minutes and stagger at 5 minutes from one server to the other.

Configuration

Configure the mail-import.properties file as follows: 

dcma.importMail.cronExpression=0 0/10 * ? * *
 dcma.importMail.mailProcessCronExpression=* 0/10 * ? * *

File name length restriction

Use the following formula to determine the maximum file name length that Transact supports for email import: 

Length[UNC_FOLDER_File_Name_Path] < PERMISSIBLE_LIMIT_PATH_LENGTH_WINDOWS - PDF_PROCESSING_FOLDER.length() - 10

where: 

PERMISSIBLE_LIMIT_PATH_LENGTH_WINDOWS = 259
PDF_PROCESSING_FOLDER.length()= 22

The following case study provides an example of this formula in the application:

  • During the import process, the !!!mail.pdfis file located in the following folder:

    D:\Ephesoft\SharedFolders\TestBatch\39455638711700

  • In this case, the maximum file name length is calculated to be as follows: 

    length[D:\Ephesoft\SharedFolders\TestBatch\39455638711700!!!mail.pdf] < 227