Question
Slegers Consulting B.V.
NL
Last activity: 12 Jul 2024 10:48 EDT
Service email request header fields not mapped to clipboard
While processing incoming email via graph API with email listeners in Pega at a customer's implementation, emails are picked up and processed as expected. However additional header fields like "Return-path" and "X-MS-Exchange-Organization-Network-Message-Id" are not mapped, while configured in the Request message header.
Another issue is that we are planning to work with aliasses from the actual mail addresses to which customers can send their requests, while the actual mail addresses are connected to Pega via listeners. This to avoid te hugh amount of listeners to be built to cover all alias mail addresses. While the inbound mail header in the actual mail addresses mention the alias in the "To:" field, not the alias but the actual mail address is mapped to property .pyInboundEmail.pyTo. However we need the aliasses to be mapped in order to do some proper routing in Pega.
I checked all possible Pega documentation and community topic on this, however did not find any proper solution on this.
Could you please help us out here. You can contact me by mail or telephone in case of any question.
Thanks in advance!
Accepted Solution
Updated: 12 Jul 2024 10:48 EDT
Pegasystems Inc.
IN
@Roberto Burgos that's not what I meant. You can add Headers on Service email rule and MS365 via Graph API will read those headers. What we have seen is there are certain headers that originate from other email clients, e.g. Gmail, and when that comes through MS, those headers are lost. If you think there's an issue with reading email headers, best to raise support request. You'll be able to add loggers and see for yourself what all email headers are being read.
Pegasystems Inc.
IN
@RonS16915269 custom email headers may not get through to the Graph APIs.
For your other question, the actual email address would be set in 'To:' header always. To access the alias email, one way we use internally in Emailbots is to access pyListenerPage (pyListenerPage.pyAccountName) which has info of which Email account(configured in Pega) caused the Email service activity to be called. Then we are able to backtrace and read the alias from the Email account.
Vodafone DE
DE
@VikasRaidhanDoes this means that if the Email Listener is configured to listen to a MS 365 mailbox, There is no chance to get any other header mapped in the Request tab of the Service Email Rule?
Accepted Solution
Updated: 12 Jul 2024 10:48 EDT
Pegasystems Inc.
IN
@Roberto Burgos that's not what I meant. You can add Headers on Service email rule and MS365 via Graph API will read those headers. What we have seen is there are certain headers that originate from other email clients, e.g. Gmail, and when that comes through MS, those headers are lost. If you think there's an issue with reading email headers, best to raise support request. You'll be able to add loggers and see for yourself what all email headers are being read.