SMTP dialogue results in unexpected errors/How-to get debug logs
The customer is integrating Pega Marketing with MailJet SMTP relay service. This is a scalable SMTP solution that should work with the Pega email integration. They ave configured an email account and have successfully sent emails from Offers.
Some of their email traffic is resulting in unexpected errors. They appear to be getting some responses that Pega Marketing is interpreting as SMTP 530, 535, and 550 responses. These are logged on instances of Data-Corr-Email which implies that the responses were recorded synchronous with the SMTP dialogue. Unfortunately the native responses from the SMTP MTA are lost.
The customer urgently needs to know how to debug the JavaMail implementation within the Rule-Utility-Function mailutilities.sendmessage. The team at Mailjet need to know the specific errors returned by their server.
No errors are logged - in fact, this is was the customer wants to activate.
Steps to Reproduce
To get the required information, DEBUG logging has to be activated on "com.pegarules.generated.pegamkt_mailutilities_mailutilities".
0% found this useful