Managing email integrations
The following topics provide information on managing your email integration,
including troubleshooting your email configurations, filtering autoreply messages, and
optimizing the performance of your email listeners.
Autoreply message filtering Pega Platform filter autoreply messages, such as out-of-office notifications or bounce-back messages, by using the following logic.Best practices for optimizing email listener performance Restarting the email listener Throttling during email processing Troubleshooting email listeners Deleting an email account Email conversations Work-.SendEmailCorr local action, and requires an Email Account instance, Service Package data instance, Email Listener data instance, and a Service Email rule. (For an example of the service rule, review the standard rule EmailDefault.Work-.ProcessEmails .)Email-based work processing pzEmailActions , which applies to Work- , belonging to Pega-ProcessEngine RuleSet . The approver receives an email that contains hyperlinks to non-local flow actions. The approver clicks on the appropriate flow action and adds comments as needed, then sends the response. The email is received by an email listener that validates the response using the service activity pyCreateAndManageWorkFromEmail , then delegates processing to the pyProcessEmailRequest agent. A copy of the response is attached to the created work item.Sending encrypted email @baseclass.SendEmailNotifcation activity and selecting the EncryptMessage parameter. For an example, see the Pega Community article Sending encrypted email . Sending digitally signed email Automatic resends Pega-ProcessEngine.pyEmailMaxResends system setting.Working with SSL-enabled endpoints Initial Email Account instances (Data-EmailAccount) Pega Platform includes two standard email account instances: Correspondence rules and email