At 10:02 AM -0500 11/7/01, Andreas Huttenrauch is rumored to have typed:

We do not wish to see bounces - just let SmartList take care of them.

That is, IMHO, not a smart way of doing things; SmartList is good, but depending on your settings, it likely won't unsubscribe sam@falcon.com when receiving a bounce on sam@mail.falcon.com (ever look at an @home bounce?). Also, SmartList won't catch multiple bounces to the same server, so an address may bounce 8,12,16, or more times before being unsubscribed, even if your minbounce is set to 4. So a human _should_ be periodically reviewing the bounces to make sure there isn't a problem anywhere. (Even if you simply drop them to a disk file and occasionally grep for, "Not confident enough to autoremove" you can keep your list a whole lot cleaner than if you ignore the X-Diagnostic: headers that SmartList handily gives you in those bounce copies.) That said, it's simple enough to write a recipe to send them to /dev/null, should you really be determined to stick your head into the sand and not see them. I'd think the simplest way is to drop them from the listowner's .procmailrc. But if you are REALLY determined to do it from SmartList, read rc.request and .bin/procbounce carefully. Charlie