Combatting Spam

I've been receiving a rather large amount of spam on a daily basis for at least the last couple of years. It started off with about 150-200 a day but has recently peaked at a regular figure closer to 1000. In fact, once or twice it's been closer to 1500. Anyway, with broadband I never really concerned myself too much about it and let my email client and the filters I had set up within it sort them out. However, it still wasn't sorting them all and I'd still have to trawl through at least 100 a day to make sure there wasn't any genuine emails getting caught.

Anyway, I finally decided to try and sort it out a bit better; with the intention of stopping the spam even getting as far as my inbox. I had a poke about in my domain control panel and thought I'd figured it out. Rather than redirecting all unqualified domain addresses to the main account I told it to filter them first; searching for certain prefixes. Anything that didn't match the prefixes would be bounced. Testing seemed to back me up.

However, thanks to Mondrak, I managed to discover that it was blocking all emails except the ones I had originated from my own PC, either via the email client or via any of the web mail services I have access to. After further tweaking I managed to eventually solve that problem only to run into a different one. The way the filters have been designed means that as well as allowing bowch@ as a valid prefix it would also allow notbowch@ or fakebowch@ or any other prefix ending with bowch@. Setting filter options that would solve this wasn't working. Everytime I set it to read "Does Not Equal" it would change to "Equal" for no apparent reason.

I have ended up setting up extra email accounts and telling the server to forward them to my main account. Any unqualified emails will now get bounced back with a failure message. Valid email addresses now only include bowch (at), blog (at), useful (at), webmaster (at) and yahoogroups (at) with everything else bouncing. I've set them up with relatively low disk quotas and will hopefully not need to change much. I'm going to keep an eye on it over the next couple of weeks and make sure that it forwards okay and isn't eating up valuable space on my domain server.