P&D Service Component Email Error response handling
Answered
Often, a document being handled by P&D email scheduler will contain an invalid email address. The address is rejected by the mail server on the receiving end and an error email is sent to the assigned address in the service component.
There is no P&D error handling for this condition, so despite the error occurring the first time, the message just keeps getting sent out to the invalid recipient and will forever cause error emails out of the service component until it is fixed. What's worse, if the email address is not editable for some reason in B1, there is no way other than excluding the document explicitly on the mass delivery definition to stop the error cycle.
I have several clients with frequent email deliveries (every 5 to 15 minutes) When these errors occur over a weekend or after hours, there can be hundreds of error emails for the same invalid recipient.
Is it possible to create a max retry attribute as a way to handle these errors? 1 or 2 email notifications are enough for an admin to manage, but when these come in such large numbers, they tend to treat the messages like spam and ignore them.
-
Official comment
Hi Kevin,
It is possible to use mass delivery where condition + UDF to filter out things you do not wish to send + use the SQL to also find what do not have emails (or use SQL RegEx to find it)
You can then set up an internal delivery of what docs- are not able to send...Thanks, Naama -
All of my mass delivery schedules use conditions defined in the module where clause. The problem is that these documents are causing errors on the mail side that is not being recorded back to the mass delivery log or the document. These are mail recipient errors like "recipient not found"
What I'm asking for is that when the recipient mail server responds with an error, that the error be recorded by the service component. That way I CAN use the where clause to filter these messages out. Obviously, the service component is capturing and handling the errors, because I'm getting emails from it whenever these errors occur. It would be better though, if it could handle these in a different way by writing the failure back to the message log.
Please sign in to leave a comment.
Comments
2 comments