8.6

from most emails sent to it. This is due to a technical limitation that will be resolved in a
future version.
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 and
/ppemail[1]/body[1]/@html respectively.
With %t%O\xmlget('/ppemail[1]/body[1]/@html',Value,KeepCase,NoTrim)
and %t%O\xmlget('/ppemail[1]/@rawemail',Value,KeepCase,NoTrim)
We get both the body and the whole raw email.
l Attachments:The input task loops through each attachment and sends them down
through the process. While the Envelope is not available, the Job Infos contain pretty
much all of the information you would get from it.
SMTPInput task properties are as follows:
l Data location:Determines what files are sent into the process:
l Envelope:Only the request envelope is sent to the process (see above).
l Attachments: Each attachment is sent down the process (see above).
Page 241