Prioritize Bounced Email Notification

+1

+1
We have the same problem as you.
It's a shame that Zendesk can't handle this, even though it was possible for simple email operations.

I understand that not all errors can be received by the mail sending server.I would like to be able to detect and notify you even if there is an error in the email sending server.
This issue is critical because Zendesk support primarily handles inquiries via email.

Please take immediate action.

We also urgently need this feature and I can only agree with the previous speakers. Zendesk no longer responds at all. I have no understanding for that.

WOW 7+ years this has been on the radar with no signs of it being completed. 

We really need this feature!! 

+1 please. 

1263082082709 any update on the above? Still a big issue within our organisation. 

Potential partial workaround for people using API/automations: loop end users, loop their identities, add undeliverable identities to an array (i.e. objects with the user id, identity id, and identity value).

How it works: We have a Tray.io workflow that generates proactive tickets to existing customers added to a list after routine events. After generating the ticket it calls the Zendesk API to find out if the 'undeliverable_count' isn't zero for any of the identities associated with an end user, and if any are it will add that to a list, which is included in a workflow run results emails so we can debug separately. 

This is kind of a partial, brute force bounce reporting workaround that provides the number of times a soft-bounce response was received at that address. Caveat - I don't think that the count will include the results of the ticket during the run, but I added a manual time delay between ticket creation and the identity check to see if that helps.

I'm hoping there's a way to just query the identities on their own, but I don't think you can without looping through however many tens of thousands of end users you might have. I posted to find out -  

https://support.zendesk.com/hc/en-us/community/posts/7739697023642-Undeliverable-identities-identity-API-end-point

We need that functionality as well. We might be forced to leave Zendesk if we have no failsafe for a misspelled recipient's address.

Hoping Zendesk sees this is a highly requested item and an important check point in the reliability of their product and their accuracy rate.  ETA would be much appreciated on this roll out.

I've seen this thread for years.  Where is this on Zendesk priorities now?  7 years later