Various Spam Issues and the Appropriate Steps to Resolve Them: Symptom: Users of the domain are getting a large amount of spam Problem: Spam sucks… Resolution: Outsource spam to MXLogic, Postini, Katharion, etc., limit incoming traffic over port 25 to the IP scheme of the outsourced service and use whatever form of message hygiene is built into the server for a layered approach (eg – Intelligent Messaging Filter in Exchange, Spam Assassin in Mac OS X Mail Server, Kerio Spam rules, etc. Symptom: An IP or domain name is getting flagged as being a spammer although the users do not send spam. Problem: The mail server potentially does…
-
-
Kerio: Spam Options
Kerio has a variety of features available for mitigating the evil spam gremlins. These include: 1 – SpamAssassin – Open Source spam filter 2 – Directory Harvest Attack Protection – track email coming in for non-existent users and limit the number allowed per host 3 – Policies – tag emails with X-Spam headers, then use local policies, etc. Also write custom filters that identify certain keywords as spam 4 – RBL – A standard with mail servers, Realtime BlackList servers mark common spammers or hosts that do not meet a minimum criteria for being acceptable mail servers 5 – SPF – Rely on srv reccords from domains to specify what IPs…
-
SBC Spam Prevention Falls Short
SBC sends all their residential customers port 25 traffic to their mail server, regardless of the destination IP number, regardless if dial up, DSL, etc. Expect this trend to continue to other vendors with residential accounts to help combat spam. IMHO killing spam by effectively blocking out port 25 for end-users is not a huge deterrent of spam.