The Get Email activity is a starter activity. When an orchestration that starts with an Get Email activity is deployed to the Integration Appliance, the Integration Appliance polls the POP3 server for email message or messages for the specified account at the specified interval.
The polled POP3 server and email account is defined in the email endpoint associated with the Get Email activity.
During run time, the Get Email activity polls a POP3 server for incoming email messages of a particular email account, as shown in the following diagram.
Protocol exception: com.jscape.inet.pop.PopException: Error in TOP 671 0: -ERR The requested message is no longer available; it may have been deleted.
To access the attachment of a incoming email message, you must add a Read MIME activity in the orchestration after the Get Email activity as shown in the preceding figure. In addition, you must map the two output parameters of the Get Email activity to variables in the orchestration and then map those variables to the input parameters of the Read MIME activity. During run time, the Read MIME activity reads the MIME Header and the body of the message and then breaks up the attachments contained in the body of the message and places the result into the parts XML output parameter. For more information, see Read MIME Activity.
Field | Description |
---|---|
Subject matches | Enter a regular expression that matches the subjects of email messages that start an orchestration job to process the email message. In the regular expression, you can specify a combination of characters and wildcards. |
From matches | Enter a regular expression defines the sender email address of the email messages that start an orchestration job to process the email message. In the regular expression, you can specify a combination of characters and wildcards. |
Regular Expression | Sample Text | Result |
---|---|---|
*hello* | hello | matches |
*hello* | hhhellooo | matches |
hello | hello | matches |
hello | hhhellooo | does not match, has to exactly match the regular expression string: hello |
hello | ello | does not match, has to exactly match the regular expression string: hello |
?ello | hello | matches |
?ello | jello | matches |
?ello | ello | matches |
Field | Description |
---|---|
Retry | |
1) Wait __ second(s) between each retry. | Specifies the number of seconds that the Integration Appliance waits before trying to establish a connection to the POP3 server. |
2) Try to connect __ times before failing. | Specifies the retry count - the maximum number
of times the Integration Appliance attempts to establish a connection
to the POP3 server before issuing an error. If an orchestration that starts with a Get Email activity is deployed and the Integration Appliance cannot connect to the specified POP3 server, the Integration Appliance logs the connections errors as warnings in the system log until the retry count value is reached. When the retry count is reached, the Integration Appliance logs an error in the system log, resets the connection error count to zero, and continues to attempt to establish a connection to the POP3 server. For example, you set the retry count to 3. The first, second, and third connection errors appear in the system log as Warnings. The Integration Appliance logs the fourth connection error as an error and resets the connection error count to zero. Therefore, the fifth connection error generates a warning in the system log. The Integration Appliance continues to attempt to establish a connection to the POP3 server. |