We use puremessage here as a smtp gateway so it stops spam coming in and does not need to integrate with anything. It plus 2003's built in spam protection are covering us here very well now.

We use puremessage here as a smtp gateway so it stops spam coming in and does not need to integrate with anything. It plus 2003's built in spam protection are covering us here very well now.
Here we use Exim, Spamassassin and Sophie (sophossavi) with a ruleset that is updated nightly. I get on average one spam a day now. Any false positives are usually due to badly configured servers. I had to admonish the EMA department of DFES because their system was sending out messages with the To: and Subject: headers replaced by "To :" and "Subject :" (not to mention the fact they were sending out passwords in plaintext!)
Users eh! grrrr.. ;-)
Its not going to eliminate all spam problems overnight but id like to recommend implementing SPF. With exchange 2003 SP2 this is simply a couple of check boxes (plus an extra dns txt record) and if everyone implemented it spam would greatly be reduced.

Sophos do a hardware unit as well as a Software solution.
Ah but isn't that the problem with SPF.. it needs to be enabled everywhere? 8OOriginally Posted by JamesC
Yea that's true Teddy, like I said if everyone implemented it spam would greatly be reduced. It doesn't take long to configure, I cant work out why more people haven't done it! I've enabled checking on my exchange 2003 box, it took all of 30 seconds. I've also created my own spf record to allow others (that have also enabled spf checking) to verify that only mail sent from my ip is legitimate email for my domain. If they have spf enabled and someone tries to spam using my domain name (but from another ip like their own or a hacked machine) then the mail should be rejected.Originally Posted by TeddyKGB
There are currently 1 users browsing this thread. (0 members and 1 guests)