Is it possible to track a reply to an incoming email to pega and have an alternate path (e.g. suppress the service case creation - we create a service case as soon as an unique topic is identified) for the same. Currently the email channel that we have setup in our application is identifying the reply to an original incoming email as a brand new email and creating a new ET, I and S case.
Have seen that there is a property pyInReplyTo which maps to the <In-Reply-To> element in the header of the incoming email. However, the original email does not have a pyMessageID set to track back the reply.