We've got a web app with nothing fancy in terms of email notifications. It would be nice to know if an end user entered email address is errant and deliveries to it bomb.
In the modern world of spam infected email, is it still worth trying to catch bounces? In mail server configuration today, its generally considered best practice not to send back bounce emails for unknown recipients due to backscatter, etc.
So, is trying to catch any delivery failures outside the simplest cases (like bad domain, which your local outgoing email server should be able to tell you) really worth the effort?
If you are sending email notifications to registered users you should do a email verification on signup to make sure they give you a legit email account.
Tracking bouches can be useful depending on your business. If it's very important that your emails to users gets received, like in the case of notification of payments due or sent, then it's worth the effort to track and report of failed emails. Helps save customer support time dealing with people complaining about not getting paid or forgetting to pay and claiming they were never notified.
I once worked at a place where this was the case, we setup a 3 strikes system that after 3 failed/bounced emails we would lock the users account and require them to reverify a valid email to continue to do business with us.