Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

Email Listener - DSN data can not be read



In the Service Email rule, set up Delivery status notification (DSN) data and set the original-to parameter. Expected result is to get all the invalid email addresses that were invalid.

Error Messages

Not Applicable

Steps to Reproduce

  1. The use Pega to send an invalid email address and trigger a bounce back email from the server..
  2. race the service page and check the pyOriginalTo field to check the original targeted email IDs.

Root Cause

A defect or configuration issue in the operating environment:

In the DSN data section, the value for 'Map To Key' column for the field 'original-to' is wrong. It should be '.pyInboundEmail.pyOriginalTo'


Perform the following local-change:

1. Configure the email listener with process Delivery Status Notification checked (DSN).

2. Configure the email service and DSN header data as shown below:

3. Two values to check for on the above page:

1. In Message Header section: Field-Name - Thread-Topic, Map to - ParseThreadTopicHeader, Map to Key - .pyInboundEmail
2. DSN data section: Field name - original-to, Map to - Clipboard, Map to key: .pyInboundEmail.pyOriginalTo
4. After the above settings and configuration is done, restart the listener.
5. Trace and observe the value in the pyOriginalTo field of the service page, it should be email id which was the recipient of the original email which could not be sent.

Published May 4, 2017 - Updated October 8, 2020

Was this useful?

0% found this useful

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us