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
We have updated the Too Old permanent failed event to include the last temporary failure code and message response that preceded this timeout of our retry period. These are found in event data as delivery-status.last-code and delivery-status.last-message
-
olo
commented
I also get this error quite often. Sending from different domains to different recipients.
"severity": "permanent",
"log-level": "error",
"delivery-status": {
"enhanced-code": "",
"description": "",
"code": 602,
"attempt-no": 31,
"message": "Too old",it's simply to general for troubleshooting.
Anyway, this error shouldn't appear at all -
Bas Luksenburg
commented
Current messages are not at all helpful. No clue what happened.
-
Keerthi commented
I cannot stress enough, We need more details. "Too old" is very generic, and does not add any value to resolving issues. We have to connect with mailgun support for every single email that failed and we have a bunch of them, the reasons vary so its important to provide as many details to our team. "Too old" does not give me details and its frustrating when I see this in the delivery status.
-
John
commented
I have been facing the same issue, been trying to get this issue resolved for almost 3 months to no avail, can't even get through first level support and had very little communication. Would appreciate some kind of respond from mailgun.
-
Jonas Dickel
commented
We were facing this issue as well. It was an internal issue from mailgun. The IP address of their SMTP was disabled so the mails were not able to be sent.
The customer support resolved the issue after 6 days of being unable to send any mails from that domain.
-
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.