When Irwin asked, L> How do I stop smartlist from automatically removing users since the bounces L> aren't their own fault? Charlie responded, S> Slow down a sec...if the address really _is_ bouncing, it doesn't matter S> who's "fault" it is, it's putting unnecessary load on your server, and S> wasting bandwidth since the mail _will_ come back to you anyway. When I saw Irwin's post, I had the impression that he was discussing this case: member A posts; member B's address is unreachable; B's site sends an NDN to list-request; SmartList sees A's address in the NDN and counts the bounce against A instead of B; after a few posts by A (fewer if more than one member is bouncing with confusing NDN's like B's) SmartList removes A. Mean- while, B remains subscribed and more and more of the active posters are get- ting removed because B's copies of their posts bounce. But A's address is working, A is receiving the list, A and B are different people, and A is not the sysadmin at B's site, so the bounces from B's ad- dress that SmartList is blaming on A are, as Irwin said, not A's fault. Irwin's question, if I understood it right, could be phrased as, "How do I stop SmartList from automatically removing users, since the bounces are not from their addresses?" That's happened a lot and it is arguably SmartList's biggest fault: being too cocky about whose address is bouncing. I've been kicked off the Procmail and SmartList Lists several times (before they were switched to Mailman) be- cause somebody else was bouncing. For a while I had to resub the Procmail List every three or four days and keep backup subscriptions at an address from which I never posted to make sure I didn't miss posts. Charlie qualified, S> ... if the address really _is_ bouncing, ... and that's the thing: it isn't.