The thread about SPAM makes me pose the following question: How do you guys handle incoming SPAM, either at your personal account level, the business/corporate level, or both? (I don't mean, how do you keep from getting spammed in the first place. This is an entirely separate topic.)
I can enumerate the following strategies for fighting SPAM at the receiver end:
1) Nothing special. Manually hand pick valid emails from the spam. Delete the spam manually.
2) Identify SPAM-receiving "dirty" email addresses and phase them out: re-register a new "clean" address at any sites that *must* have a current address for you. Eventually, ignore dirty addresses.
3) Use a custom domain name of your own choice and use with it a mail server that allows all emails that end in that domain name to go to a designated mailbox. (This allows you to "create" new email addresses ad hoc by simply inventing a new name prefix.) Create a "new" custom address in that domain for every single purpose for which you need an email address. IE, an Amazon account would have amazon@me.com; Ezboard, ezboard1@me.com; etc.
4) Direct "dirty" SPAM receiving email addresses that are no longer used, to generate a bounce back to the sender.
5) Direct "dirty" SPAM receiving email addresses that are no longer used, to a "black hole".
6) Baysian filters at either the email server end or the POP client end.
7) Any of the "whitelist" based or challenge/response based email systems that generate an authentication message back to the sender in order to confirm whether there is a human behind the enter key. Examples: Choicemail, MailGuard, BrightMail.
My personal choices: 2, 3, 4. Reasons: simplicity and ease of management. The use of a custom domain name to identify usages of email addresses is a keystone of my approach. I don't need to "register" a new address anywhere, each address is invented by me for a role or a purpose.
I don't "believe" in Baysian filters. Anecdote: I recently had an experience where a business card had the person's personal email address printed on it, but he didn't get an email I sent to that address. When I finally called him on the phone he said that my message was trapped by anti-spam measures soo he added me to the whitelist and finally replied to my message. The header of my message (in his reply) said "Baysian Filter Caught Suspected SPAM". So in other words, a Baysian filter stupidly flagged a human written email as SPAM...
And I don't buy into challenge/response systems. I used to rely on a "bounce" message that contained instructions to resend to a correct address, a rudimentary form of challenge. I had a few people who received this message who were just computer illiterate enough (AOL users

) that they just didn't bother again because they were too confused. That's my objection: challenge/response is not intelligible to many end users.
Any thoughts?