In this field... | Specify... |
Host Name | Name of the machine on which the mail server is running (for example, mailserver.company.com). This must be the same mail server you identified when creating the outgoing mailbox in the AR System. |
Type | Type of mail server. Select POP3 or IMAP. |
User Name | User name of the user to which the Remedy e-mail notifications are sent. This must be the same user name you identified when creating the outgoing mailbox in the AR System. |
Password | Password associated with the user name. Note: Passing a user name and password in an e-mail message presents a possible security exposure. While the e-mail message resides on the POP3 or IMAP server, someone might be able to access this information. |
Time Interval (seconds) | How often (in seconds) the Email Listener port is to check for incoming e-mail messages on the POP3 or IMAP server. |
Port | Port to use for the mail server. The default for POP3 is 110; the default for IMAP is 143. |
Log out after each mail check | For use with IMAP and multithreading only. If you select Yes, Integration Server logs out a read-only thread to the IMAP mail server after checking for mail on that thread. The main read/write thread to the IMAP server remains intact. If you select No, all the read-only threads remain intact. Select Yes if your IMAP server restricts the number of connections it will allow to remain logged in. |
In this field... | Specify... |
Run services as user | If you selected Yes in the Require authorization within message field, the Run services as user field remains blank because the Integration Server expects the user name and password to be in the e-mail message. If you selected No in the Require authorization within message field, you must enter the user under which the service is to run on Integration Server. |
Require authorization within message | If you select Yes, Integration Server checks for $user and $pass parameters in the Subject line of the e-mail message. The user name is the user under which the service is to run on Integration Server. If you select No, you must specify the user in the Run services as userfield above. |
In this field... | Specify... |
Global Service | Service to be executed on Integration Server. This field overrides a service specified in the Subject line of the e-mail message. Specify the service you created to handle the e-mail notification either in this field or in the Default Service field. |
Default Service | Service to be executed if the e-mail message does not provide a valid service in the Subject line and the Global Servicefield is blank. Specify the service you created to handle the e-mail notification either in this field or in the Global Service field. |
Send reply email with service output | Whether you want Integration Server to send output generated by the service to the original sender in an e-mail attachment. If the original e-mail contained multiple attachments, the reply contains an equal number of attachments. |
Send reply email on error | Whether you want Integration Server to report errors that occurred during service execution to the original sender in the Body portion of an e-mail message. |
Delete valid messages (IMAP only) | Whether you want Integration Server to delete a valid e-mail message from the IMAP server after Integration Server has successfully received the email message. This setting helps prevent e-mail messages from accumulating on the IMAP server, possibly affecting disk space and performance. Integration Server always deletes e-mail messages on a POP3 server. |
Delete invalid messages (IMAP only) | Whether you want Integration Server to delete invalid e-mail messages from the IMAP server. Invalid e-mail messages are those that experienced errors during processing. This setting helps prevent invalid e-mail messages from accumulating on the IMAP server, possibly affecting disk space and performance. Integration Server always deletes e-mail messages on a POP3 server. |
Multithreaded processing (IMAP only) | Whether you want Integration Server to use multiple threads for this port. This setting allows the port to handle multiple requests at once and avoid a bottleneck. |
Number of threads if multithreading turned on | The number of threads Integration Server is to use for this port. The default is 3. |
Invoke service for each part of multipart message | Whether Integration Server should invoke the service for each part of a multipart message or just once for the entire message. You must specify Yes to have Integration Server treat each part of the message individually. That is, Integration Server sends each part to the content handler and then to the specified service. |
Include email headers when passing message to content handler | Whether Integration Server includes the e-mail headers when passing an e-mail message to the content handler. Because you select Yes for Invoke service for each part of multipart message, you should select No for this option because each section has its own headers that the content handler and/or the service already knows how to process. |
Email body contains URL encoded input parameters | How Integration Server treats input parameters it finds in e-mail messages. When this field is set to Yes, Integration Server considers a string such as ?one=1+two=2 to be a URL-encoded input parameter. It then decodes this string into an IData object, puts it into the pipeline, and passes it to the service. When this field is set to No, Integration Server treats the string as plain text and passes it to the appropriate content handler. |