About to pass a dubious milestone …

[update: 8:49am 27-Jan-2009] Yup … my spam-box is at 20012 and counting.

[update 2: 8:29am 31-Jan-2009] 25188 and counting … wassamatta, they couldn’t get me to 30k by the end of the month (16 hours away)? Sheesh …

On a positive note, Thunderbird is able to handle 25188 email sized box without problem. I remember when 1000 emails would give email clients fits …
——————————————————————–

Our spam filter is a pipeline. It can handle quite a load … we have been email bombed before, and far from causing the server conniptions, it handles it quite well.

It tags our mail with a big old [SPAM] in the subject, and other filters redirect this to a specific (per user) mailbox.

The mail system discards most of the spam, based on a variety of rules. The roughly 5% of mail that makes it past these rules (and yes, we monitor their effectiveness) runs through our filters.

Spam goes into the spam-box. Every month I marvel at the growth. Recently I was amazed that we had crossed more than 10k spams into my personal spam box.

Recently.

As of today, my spambox for the month of January, is 19211 spam.

And growing.

20k here we come.

In the 5 minutes I have been typing this, I have received ~8 spam into the box.

Amazing.

Viewed 14205 times by 3194 viewers

3 thoughts on “About to pass a dubious milestone …

  1. You should consider using postgrey (if you aren’t already). It works great for us, the spam never reaches your machine. If you do enable it, watch the logs for false positives though (a lot of mail servers don’t follow the RFCs).

    http://postgrey.schweikert.ch/

  2. @Scott

    We had used it in the past. Unfortunately, broken MTAs like Exchange, didn’t deal well with Postgrey, and I would get lots of customers complaining of bounced messages. The correct behavior hasn’t been programmed into Exchange as far as I understand (it deals incorrectly with 450/550 messages as compared to how it should deal with them).

    So rather than have pissed off customers, we pulled postgrey out.

    Not our fault, not postgrey’s fault. Its Exchange.

    I am not hopeful that Microsoft will ever fix this.

Comments are closed.