2020.1

Example
In this example, the SMTP Input plugin is used to capture incoming emails data that must meet
certain conditions as the subject that contains "Work to do" and the sender that contains
"[e-mail] ". The process then redirects the content of those emails to an extraction
and finally to a PDF printing.
Input
The SMTP Input task does not, by itself, capture any files. Neither does it directly wait for
requests to be received. Actually, it is the SMTP Server service that receives the requests and
places them in a specific location on the drive. When a request is received, the SMTP Input
polls that location and finds the requests and all attachments. It will always pick up the "oldest"
request received.
Warning
Due to a technical limitation the SMTP Input task does NOT receive the BCC addresses
from most emails sent to it.
Processing
The task reads the incoming SMTP request and provides the data within its body.
Output
Depending on the Data Location option, the output is different:
l
Envelope: The request file in XML format, including all email fields (from, to, cc, bcc,
subject, body) as well as additional header fields (email client information, attachments,
etc). The message body and attachments are available through specific XML attributes.
These files do not have the full path, but you can use the %t%O variable to get the current
temporary folder where they are located.
Tip
Suppose we have two files named in the XML file under /ppemail[1]/@rawemail
Page 372