This documentation applies to the 8.1 version of Remedy Action Request System, which is in "End of Version Support."

To view the latest version, select the version from the Product version menu. file


The term email daemon is frequently used when discussing the internal components of the Email Engine. For example, "email daemon" is used to describe background processes launched at start-time, email "handlers," the use of various threads to carry out different tasks like sending and mails, parsing instructions, and so on. In UNIX, these background processes are usually called "daemons," whereas for Windows they are called "services." Following the UNIX convention, the file you use to set parameters for the Email Engine is called For the most part, the Email Engine as synonymous with the email daemon.

When the Email Engine is installed, the file is created in the Email Engine installation directory and is populated with the name of your organization's email server, user name, and password. The main purpose of the file is to identify the AR System server your Email Engine communicates with.

Sample contents of file

(Click the image to expand it.)

To use the file, see Settings in the file.

Updating the file

If your email environment changes — for example, if you need to change a server name or a TCP port — the file must be updated. The following procedure explains how to update the file.

  • To update the value of one property at a time, open a command prompt, navigate to the Email Engine installation directory, and execute the following command:

    For Windows:

    "JREInstallDir\java" -cp jarFileNamesSeparatedBySemicolons;
    com.bmc.arsys.emaildaemon.EmailDaemon parameter

    For UNIX:

    JREInstallDir/java -cp jarFileNamesSeparatedByColons:
    com.bmc.arsys.emaildaemon.EmailDaemon parameter

    JREInstallDir is the path of your JRE installation.

    jarFileNamesSeparatedBySemicolons or jarFileNamesSeparatedByColons are the jar files listed in the command line of the command line from EmailStart.bat or file.


To use this command, you must properly set the library path for all UNIX platforms.

  • To update the values of multiple properties simultaneously, add them to EmailStart.bat (Windows) or (UNIX) and running the executable.

Email Engine startup parameters




Server where the email forms (and the configuration information) are located.


User name


AR System Application Service password. The Email Engine requires the same password that is supplied on the Connection Settings tab of the AR System Administration: Server Information form. To avoid authentication failures, the application password must not exceed 20 characters.


TCP port for the server to which the Email Engine should connect.


RPC number of the server to which the Email Engine should be connected. Use this parameter to connect to a private server. This can enhance performance if you expect a high volume of mail.


Language to be used. (The default is C.)




Directory where the file is located. If this parameter is not supplied, the system assumes that this file is stored in the same directory as the emaildaemon.jar file.


Time interval (in minutes) to use when checking the server for configuration updates (modifications to records in the Email Mailbox Configuration form). The default is 30 minutes.


Encrypts the given string and returns the value to the command line.


The temporary directory to be used for internal Email Engine files.


Monitor module interval (in minutes) to wait before trying to start the Email Engine again. The default is 30 minutes. When the AR System server is not available, it tries to restart the system for every 30 minutes by default.


(For 32-bit JVM only) MAPI sent folder where sent mail should be stored.


Displays the client version; does not take any parameter.


Changing property values does not affect the current instance of the email engine. To use the updated property values, you must restart the email engine service manually. When using EmailStart.bat or to restart the service, make sure to remove all the parameters you used to update the property values.

This version of the documentation is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.


  1. Laurent Matheo

    Hi (smile)

    It seems the page "Settings in the file" is broken? It gives this message:

    (something like "you can not display this page

    Restrictions have been applied to limit access to this page).


    Vous ne pouvez pas afficher cette page

    Des restrictions au niveau des pages ont été appliquées pour limiter l'accès à cette page.


    May 01, 2013 03:04
    1. Aparna Saxena

      Hi Laurent, thank you for your patience.

      The "Settings in the file page is now available for you to view.




      Jun 18, 2013 11:51
  2. Aparna Saxena

    Hi Laurent, thank you for your comment!

    We are currently in the process of re-validating the contents of the "Settings in the file page, which is why it has limited access.



    May 07, 2013 05:53
  3. Lj Longwing


    How long does that validation take?  The page has been 'down' for over a month and I need access to the contents....I truly don't understand why the entire document needs to be unavailable to the user community while you edit it.

    Jun 05, 2013 08:35
    1. Aparna Saxena

      Hi Lj! We're sorry for the trouble, but the team is still working on updating these pages. We'll try and make them available to you as soon as possible.

      Meanwhile, we're also trying to see if there is a way for you to access the information while we're still working on it.

      Thanks for your patience!


      Jun 09, 2013 10:52
    1. Aparna Saxena

      Hi Lj, thank you for your patience.

      The "Settings in the file page is now available for you to view.



      Jun 18, 2013 11:52
  4. Raimo Waldvogel



    I was looking for how I could configure the Emailengine to make more then just the stdout.log, stderr.log and associated .bak files. I would like to have log files like the arjavaplugin server with a log for each day.

    Now I found to less informations here in the docs.

    For example it looks like the AREmail/log4j.xml is not used because there the logfile name javaapi.log is configured... Or do i misunderstand something?

    I find the logfile names in the armalid.bat at the end of the line:

    -out "%~f3\logs\stdout.log" -err "%~f3\logs\stderr.log" -current %3

    But here I don't find information for any of the parameters (-out, -err)...

    Can you show me where I find the information? Or how I can switch to log4j logging?


    best regards,



    Aug 06, 2014 07:15
    1. James Wagner

      Hi Raimo,

      Thanks for your comment. I will look into locating the information you are requesting. I will also forward this comment to a subject matter expert to see if it's feasible to switch to log4j logging. I'll post a follow-up as soon as progress is made on either issue.

       Thanks again - Jim Wagner

      Aug 08, 2014 04:25
      1. Stefan Hall

        Hi James, Nearly 5 years later...

        May 05, 2019 01:36