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?
Bounce Management makes a huge difference, lets say you're a company that sends 50,000 emails a month for newsletters or receipts. If a certain Email Server lets say "mx.maildomain.com", bounces an email, hard or soft. And if "mx.maildomain.com" server has advance spam filtering techniques deployed on it. And you repeatedly send the same user over and over again, because you mail out a weekly newsletters. Then "mx.maildomain.com" might decide, you're a spammer and then most of your emails will end up in the junk folder (Including your receipts to other customers on that mail server) or you can end up getting blacklisted.
But more importantly, is Email Feedback Loops , you should definitely set those up. This tells you what users clicked the "Spam" button on the email you sent out. This can be way more damaging then bounces. If people repeatedly mark your emails as spam, it's the best way to get blacklisted. I set them up for my company, even with the proper opt-out links, I couldn't believe how many people click the spam link on my monthly newsletters, they signed up to. It was shocking to see. It took a while to delete all those users from my list, but it's worth the time.