deleting on hold email addresses and making others primary

[questions]

Does anyone get rid of the old email addresses that have bounced? 

It seems like a decent thing to do.  Is there any reason I wouldn't want to get rid of them?  Right now it looks like about 10% of our total email addresses are on hold for bouncing.

Is there any easy way to do this or should I just write some sql, which should be pretty straight forward (delete from civicrm_email where on_hold).  I suppose I might want to only delete those that bounce as bad vs those that get held for quota, vacation, dns, etc.

I guess first I'd want to make sure none of the bounced addresses isn't something easy to fix like .cm instead of .com. 

Then there is the issue of primary.  I assume I'd need to manually set the primary flag on one of the remaining addresses if there is one.

Are there any gotchas I'm missing here?

[Erik Hommel]

I guess I would create a scheduled job to do that on a regular basis? In other words, create an API function and set it up as a scheduled job. Do you know how to do this or would you prefer to stick with your sql?

[questions]

Ultimately a job probably makes sense.  To begin with, I think I'd like to look over the bounces just to make sure we're not automatically deleting something that is ok or easy to see what is wrong.

I suppose I could come up with something that would report the addresses that bounced the first time they were used.  These most likely will have typos. Once a year we have fair amount of manual data entry and get a number of typos.

[JohnFF]

We've got a system on the cards to fire an sms to people requesting a new email address if it bounces. If anyone wants to help me on that then poke me!

Also, is now a good time to plug my automatic email amender? Could help you preventatively get those bounce numbers down...