Before I continue however, let me tell you that the real definitive voice on SPAM prevention in Domino is really Chris Linfoot whose site contains a wealth of information on how to prevent SPAM in Domino. Julian and Bruce did two “Taking Notes” podcasts with Chris on SPAM that you might want to check out as well.
Anyways – for most companies SPAM is a really big issue and something that turn the hair of the IT department gray. I have heard estimates to the fact that 66-75% of the e-mail traffic on the web is generated by spammers. Something to be quite concerned about.
As an enterprise there are a couple of measures you can take to protect yourself from receiving massive amounts of SPAM:
- Route your e-mail through a third-party that handles the SPAM control for you.
- Purchase a hardware device such as a Baracuda.
- Run an internal SPAM prevention server such as TrendMicro or another SMTP host with some kind of baysian filtering.
- Use DNS blacklists.
In addition to the above a new approach called “graylisting” is starting to gain acceptance. In my mind graylisting sounds very promising for the time being but isn’t yet supported by Domino though.
Common for all the above solutions are that they are either quite expensive or time consuming to setup and configure. While all of the above solutions work you can get a lot of bang for your buck using a free approach called DNS blacklisting. While the concept of blacklisting is probably well known to most, the concept of DSN blacklisting may not be. Using DNS blacklist(s) the Domino server will query the blacklist(s) for the IP address of the sending SMTP server on each transaction. If the IP address of the sending server is found in a configured blacklist the server can log the occurance or simply refuse to accept the e-mail.
Configuring DNS blacklists in Domino is easy. Simply edit the configuration document for your incoming SMTP server and go to the “Router/SMTP” –> “Restrictions and Controls…” –> “SMTP Inbound Controls” tab. Toggle the “DNS Blacklist filters” to enabled and add a couple of blacklist servers and select the appropriate action to perform when a sending server is found in the blacklist. Please not that all servers are queried – not just until a match is found so you really shouldn’t just add all the DNS blacklists in the World…
There are numerous lists of there on the web with varying quality and different levels of strictness. We normally use the below list for customer installations without any issues (again Chris Linfoot has more on the different lists):
Apart from the above lists you might want to utilize some lists that deny e-mail from know spammer nations if you do not normally receive e-mails from those countries. At the office we deny e-mails from Taiwan, China and Russia:
A complete list of country lists and information on how to use these lists are available at countries.nerd.dk.
If you are running Domino 7 you also really should instruct the Domino server to only accept e-mails to the recipients that exists in the Domino Directory. This is done on the same tab as above in the “Inbound Intended Recipients Controls” section:
To see how many connections are rejected using the blacklists you can use a Domino server command at the console:
sh stat smtp
This will produce output like the below:
SMTP.Command.DATA = 1357 SMTP.Command.EHLO = 33 SMTP.Command.HELO = 5548 SMTP.Command.Invalid = 3955 SMTP.Command.MAIL = 5693 SMTP.Command.NOOP = 3 SMTP.Command.QUIT = 1603 SMTP.Command.RCPT = 2065 SMTP.Command.RSET = 155 SMTP.DNSBL.bl.spamcop.net.Hits = 1115 SMTP.DNSBL.ch.countries.nerd.dk.Hits = 1 SMTP.DNSBL.dnsbl.sorbs.net.Hits = 2532 SMTP.DNSBL.list.dsbl.org.Hits = 163 SMTP.DNSBL.ru.countries.nerd.dk.Hits = 5 SMTP.DNSBL.TotalHits = 3867 SMTP.DNSBL.tw.countries.nerd.dk.Hits = 51 ... ...
Above you can see some SMTP statistics from a server at my office. You can see a line each of the blacklists we employ starting with “SMTP.DNSBL” telling you how many hits each list have had. Please note that the statistic for a blacklist is not visible until the blacklist have had at least one hit. As you can see we deny quite a lot of SPAM just using this simple approach.