2021.2

When using the POP3 protocol, filtering is done at the client level. The plugin loops through
every single email located in the inbox, retrieves the email’s header and applies the conditional
logic. The plugin stops that loop when a header corresponds to the conditions. Only at that
point the email's body and attachments are retrieved, and the email that corresponds to the
conditions is deleted from the mail server.
Note
When using the POP3 method, the plug-in will run very slowly if the inbox contains a
large number of emails. Always use IMAP when possible.
Emails retrieved using POP3 are deleted from the server; emails retrieved using IMAP can
either be deleted or marked as read.
Output
Once the plugin is done processing, an XML file is created with the email’s details and location
of the body and any attachments. The encoding of the XML file is Windows-1252.
The body and attachments are located in the job's Temp folder of Workflow. Within the same
process, those files must be moved to another location, otherwise they will be deleted at the
end of the process (as expected for all files in the Temp Workflow folder).
Retrieving and moving the body and attachment files may be done using an "XML Splitter" on
page469.
Example output file
<?xml version="1.0" encoding="windows-1252"?>
<Email>
<FromName>Peter Parker</FromName>
<FromEmail>[e-mail]</FromEmail>
<Subject>Bill of Lading</Subject>
<DateTime>2018-03-29 15:52:54</DateTime>
<To>[e-mail]</To>
<CC></CC>
<BCC></BCC>
<Files>
<File>
<Type>Body</Type>
<Folder>C:\ProgramData\Objectif Lune\PlanetPress Workflow
Page 363