I bought a domain a while back with my own server. I have a little shell script for one-use e-mail addresses, which adds an entry to /etc/aliases in the form "tmurray-(site name)", rebuilds the alias database, and adds another entry to a text file saying what website the address is associated with.

At my mail client, I filter each message into directories. My main inbox gets all "tmurray@" messages (mostly system e-mails and a few from friends). Then I have a few directories for mailing lists. Then there is a catch-all directory (matching "tmurray-*@"), which naturally gets most of the spam (but with a lot of ligit messages, too).

Almost all my spam comes from either one of the mailing list addresses (this mailing list didn't have address obfuscation in the archives when I first signed up) or at "tmurray-pair@" (which is on my DNS registration). It's gotten bad enough on that address that I've split off "tmurray-pair" into a seperate mail directory.

Now here is where you get to the true vileness of spammers. That address needs to be on the DNS registration. It's standard practice for good reasons. If someone needs to tell me about a problem with my domain, that's the address they'll use. However, most of what is in there is spam. Having even one false positive would be dreadful. Spammers have polluted an otherwise critical communication path into near uselessness.