Temporary directories and files


Email Engine uses temp directories to store intermediate files for email messages, attachments, and templates.

Under normal conditions, Email Engine cleans up these temporary files. However, if Email Engine terminates abnormally for some reason, you should remove these files manually. Some patterns of the temporary file names that Email Engine creates are:

Important

If you are using Email Engine on Windows, do not run the Email Engine service and EmailStart.bat at the same time.

Using the system temp directory

By default, Email Engine uses the system temp directory to manage the temporary files. You can locate this directory as follows:

  • On Windows, check the Windows default temp directory.
  • On UNIX, check the /var/tmp or /tmp directories.
  • Alternatively, use the TEMP, TMP, or TEMPDIR environment variables to identify the system temp directory on any operation system.

Using an alternate temp directory

You can make Email Engine point to an alternate temp directory, if the system temp directory does not have enough space.

To use an alternate temp directory

  • On Windows, add -Djava.io.tmpdir to the EmailStart.bat file as follows:

    "%JavaPath%\java" -Djava.io.tmpdir=<directoryPath> -cp
    emaildaemon.jar;arapi%LIBVER%.jar;arutil%LIBVER%.jar;activation.jar;mail.jar;imap.jar;
    smtp.jar;pop3.jar;armapi%LIBVER%.jar com.bmc.arsys.emaildaemon.EmailDaemon
  • For UNIX add -Djava.io.tmpdir to the emaild.sh file as follows:

    exec ${JAVA_BIN}/java \-Djava.io.tmpdir=<directoryPath>
    \-Djava.library.path=${InstallPath}
    \-cp ${CP_PATH} \com.bmc.arsys.emaildaemon.EmailDaemon
    \-d ${InstallPath} >${LogFile} 2>&1

<directoryPath> is the fully qualified path where the temporary files are created.

Best practice
We recommend that you monitor these directories for files that are no longer needed, which Email Engine does not clean up.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*