We have a requirement to pull the data from DB and send the multiple emails to multiple recipients based on the biz logic. This whole process runs in an Agent and it runs every night after biz hours. As per the settings, agent runs successfully and the emails were sent. But we see an exception while running the agent and the exception details are given below. I am not sure whether this exception stops sending emails or not. After doing some research, I did find a PDN article on this issue and the resolution for it. But I am checking like is there any alternative solution for resolving this issue without making SMTP configuration changes as mentioned in the article. We are using PRPC 7.2.2 in our application and WAS is our app server. The email server for our application is the company's standard mail server.
javax.mail.SendFailedException: Invalid Addresses; nested exception is: com.sun.mail.smtp.SMTPAddressFailedException: 452 Too many recipients received this hour ; nested exception is: com.sun.mail.smtp.SMTPAddressFailedException: 452 Too many recipients received this hour ; nested exception is: com.sun.mail.smtp.SMTPAddressFailedException: 452 Too many recipients received this hour
The error is not coming from Pega, but from an ISP or corporate email server to prevent spamming. No changes can be made within Pega to avoid the error (unless you limited the amount of emails sent per hour in your agent). Making the change mentioned in that article is likely the easiest solution.
Thank you for the confirmation. A quick observation is like this issue comes in PRD almost all the time but not coming in non prod env. Is there any specific reason for it?
Also, another question is like if we have this exception then do we see some missing emails during agent run or what exactly the situation would be? I would like to compare it with my current PRD situation now.
Are there as many emails being sent in non-prod and are they going to the same destination? One of these could be why you only see it in production.
I'm not certain how exactly Pega behaves when this occurs (it may depend on your specific configuration), but my guess is that once the error is received all emails sent after would fail to send until enough time has passed.
Thank you all for the valuable suggestions and we resolve the current PRD issue with the mentioned PDN article. Initially we had a limit of 40 emails id's per hour and now we increased to 1000 per hour. Hope this issue will not come.