{"id":2782,"date":"2015-10-01T14:50:45","date_gmt":"2015-10-01T14:50:45","guid":{"rendered":"https:\/\/ephesoft.com\/docs\/?p=2782"},"modified":"2022-03-01T12:50:50","modified_gmt":"2022-03-01T19:50:50","slug":"email-import-best-practices-multiserver","status":"publish","type":"docs","link":"https:\/\/ephesoft.com\/docs\/products\/transact\/features-and-functions\/administrator\/import-ingestion\/email-configuration\/email-import-best-practices-multiserver\/","title":{"rendered":"Multi-Server Email Import"},"content":{"rendered":"

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’s best to have them check every 10 minutes and stagger at 5 minutes from one server to the other.<\/p>\n

Configuration<\/h2>\n

Configure the mail-import.properties file as follows:<\/span><\/p>\n

dcma.importMail.cronExpression=0 0\/10 * ? * *\u00a0<\/span><\/p>\n

dcma.importMail.mailProcessCronExpression=* 0\/10\u00a0* ? * *<\/span><\/p>\n

File Name Length Restriction<\/h4>\n

Use the following formula to determine the maximum file name length that Ephesoft Transact supports for email import:<\/p>\n

Length[UNC_FOLDER_File_Name_Path]\u00a0< PERMISSIBLE_LIMIT_PATH_LENGTH_WINDOWS – PDF_PROCESSING_FOLDER.length() – 10<\/strong><\/p>\n

where:
\nPERMISSIBLE_LIMIT_PATH_LENGTH_WINDOWS = 259<\/strong>
\nPDF_PROCESSING_FOLDER.length()= 22<\/strong><\/p>\n

The following case study provides an example of this formula in application:<\/p>\n