This documentation supports the 18.05 version of Remedy Action Request System.

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

Login, Password, and TCP Port labels

The Login and Password labels identify the user name and password used when executing the instruction. You can configure exactly how the user name is to be determined for an incoming email:

  • Set a security key in the AR System Email Security form. You must add Key:securityKey to the email. If Key:securityKey matches an entry in the AR System Email Security form, then the corresponding user name is used.
  • Use the supplied user information: user login name, password, possible authentication, possible language, possible RPC, and possible TCP inside the email by using the appropriate labels and values.
  • Use the sender's email address. The Email Engine searches through the User form for the appropriate user name by searching for the email address. It uses the first user it finds whose email address corresponds.

The passwords and security keys are encrypted in the AR System Email Messages form. The aliases for Login are User, User Name, Name, and Login Name.


If you try to send an email in an HTML template, do not use a colon in the Login, Name, or Password labels. For example, do not use: Login: <input type="text" name="!536870918" size=50/> Instead, use the format: Login <input type="text" name="!536870918" size=50/> With this format, the Email Engine can parse correctly that Login is a label for a field on the form and not an instruction.

The TCP Port label identifies the TCP/IP port of the AR System server, if your AR System server is not using the BMC Remedy AR System portmapper. The alias for TCP Port is TCP.

Was this page helpful? Yes No Submitting... Thank you