Spam Rules Not Working

I used a modification to the Domino Directory (found on the Notes Net site) to reduce spam on our server, been working fine for a long time. For some reason, the server no longer relates the $DNSBLSite to the CC field. Every message that has a valid recipient address in the CC field on a message is being trapped by the rule and thrown into our spam database. I’ve upgraded to 6.5.4, replaced the database design, modified the FieldString variable in the design, but it still looks at the actual CC field instead of the $DNSBLSite field for the rule. PLEASE HELP!!!

Original post on Notes Net:

How to easily stop SPAM (Lotus/Domino 6.51)

Posted by Brad C Davis on 21.Feb.05 at 01:55 PM using a Web browser

Category: Domino ServerRelease: 6.5.1Platform: All Platforms

After months of trying different methods, I haven finally rid our network of SPAM. The following is what I did:

  1. Modified the ConditionParser in the names.nsf template so that “CC” now looks like:

Case “7”

'//CC

'FieldString=“CopyTo”

FieldString=“$DNSBLSite”

This makes it so that now a server rule stating that “When CC contains .”, move to database “caughtmail.nsf” (or whatever other database you want to use to catch spam).

  1. Add the top blacklists and make sure you hit tag and deliver.

  2. When monitoring this “caughtmail.nsf” mail database, if you see something important, simply add an EXCEPTION to this “CC contains .” rule so that when the sender contains this domain name, it does not go to this caughtmail.nsf folder.

I sincerely think this is the best way to monitor spam, and not lose any important emails. The trick is finding the blacklists that block most of the spam, and not impt email. Our SPAM problems are basically eradicated because of these rules!

Subject: Spam Rules Not Working

You may find this useful.

http://chris-linfoot.net/d6plinks/CWLT-6BTCDM

http://chris-linfoot.net/d6plinks/CWLT-6BUHHP

Subject: RE: Spam Rules Not Working

THANKS!!!

I applied the modifications indicated in your documents and I can now reference the DNS blacklist correctly on my test server. I’ll modify the production server today. I’m not sure why the other “hack” stopped working, but thanks again!