Provide meaningful delivery status description rather than "Too old"
Provide meaningful delivery status description rather than "Too old"
I'm monitoring webhooks for "permanent" failures and forwarding the "delivery-status" message/description (why are those not unified into a single field??) to my end users. Instead of merely reporting "Too old", please insert the error message from the previous "temporary" failure, so that it becomes clear what the real issue is.
Florian Bauer
shared this idea
4 comments
-
Scott Carter
commented
I'm having the same issue and would really appreciate more info on the cause without having to open a ticket.
-
Anonymous
commented
Without your comment I'd never find the real issue, because I was only look at permanent failures. That error message is really misleading, hope they can fix this.
-
Kelly
commented
Yes we desperately need this too. Half of our recipients were soft bounced due to "Too old" but we could still send to them previously on other ESPs.
-
Mike Rogers
commented
Yes please. I had to wait on support to find out why our emails weren't arriving at a specific domain. The support turnaround to provide additional detail was a few days, which really affected our relationship with the affected client in our business.