Friday, February 20, 2004 [Tweets] [Favorites]

Unwanted

Nat Irons:

As soon as modern filters become reliable enough for mainstream adoption, people are going to treat them as killfiles. It’s going to cause havoc. It’ll be hilarious! But messy.

It’s been happening for a while, and I’m sometimes tempted to do it myself!

2 Comments

I have a few SpamSieve rules that I use as to killfile against certain people on mailing lists.

Actually, this wasn't intentional at first. SpamSieve marked the first piece of mail it processed from this person as spam. When I saw it in my Spam folder, I said, "Hey, that's a good idea!" and left the rule in place. Makes for a more peaceful mailing list experience, since this person almost never contributes anything of substance.

This is another reason I prefer offline mail filters to server-side filters. I can use a client side filter to block whatever I want and it doesn't impact anybody else's filters. With an ISP level filter, I might be impacting others email experience.

Marking unwanted list messages as spam should just work. But let me clarify a few things that may not be obvious:

If you mark a mailing list message as spam, SpamSieve will add the sender to its blocklist, but it will not add the mailing list header to the blocklist. (If you mark the message as good, it will add them both to the whitelist.)

Once you have SpamSieve trained, you should turn off auto-training, and it should definitely be off if you use SpamSieve as a killfile.

Stay up-to-date by subscribing to the Comments RSS Feed for this post.

Leave a Comment