Current Release

5/1/2014: Version 5.0.1

Many, many bug fixes, including a large number of bugs that can cause crashes. spamdyke-qrv has also received a great deal of attention and now handles every strange configuration qmail can support.

Download spamdyke version 5.0.1

Previous Releases

1/28/2014: Version 5.0.0

Adds full recipient validation and some new sender filters. Also changes the whitelisting feature to not automatically allow relaying for whitelisted connections and fixes a number of bugs.

Download spamdyke version 5.0.0
View the upgrade notes

1/20/2012: Version 4.3.1

Corrects a bug in the new header blacklist filter that could cause erroneous errors and incorrect message rejections.

Download spamdyke 4.3.1

1/15/2012: Version 4.3.0

Adds the ability to filter messages based on the content of their headers. Also fixes some small bugs, a compile error on Debian 7 and a major series of bugs that could result in buffer overflows (possibly remotely exploitable, depending on the configuration options). Please upgrade immediately!

Download spamdyke 4.3.0

rDNS directories

Some of the options described below search directory structures for rDNS names. A directory structure is used because repeatedly searching a file full of domain names incurs a serious performance penalty. Querying the filesystem for the existance of a single file is very fast. Rule of thumb: if there are more than 100-200 entries in a file, consider switching to a directory structure instead.

To construct the directory path it uses, spamdyke takes the remote server's rDNS name, breaks it apart at the dots and reverses it using the following patterns:

e-five.d-four.c-three.b-two.a-one becomes a-one/b/b-two/c-three/e-five.d-four.c-three.b-two.a-one
d-four.c-three.b-two.a-one becomes a-one/b/b-two/c-three/d-four.c-three.b-two.a-one
c-three.b-two.a-one becomes a-one/b/b-two/c-three.b-two.a-one
b-two.a-one becomes a-one/b/b-two/b-two.a-one
a-one becomes a-one/a/a-one
In essence, the last three sections of the name are reversed and become directory names. If there are more than three sections, no further directories are created. Also, the first letter of the next-to-last section is used as a directory name. This is done to keep the numbers of directories per folder lower, since the "com" folder has the potential to become unmanagable. The full rDNS name is always used as the filename.

The final filename is treated as a wildcard and matches any host that ends with the given name. For example, if the following file existed in the directory structure:

spamdyke would match the following rDNS names:

These directory and filenames can be constructed with the domain2path tool, included with spamdyke. domain2path takes one rDNS name as an argument and returns the correct path to that name. domain2path also accepts a flag, -d, which makes it only return the directories in the path. This is useful in scripts:

mkdir -p /PATH/TO/DIR/`domain2path -d FQDN`
touch /PATH/TO/DIR/`domain2path FQDN`

NOTE: The names of all the directories and files used in the directory structure must be lowercase or spamdyke will not match them. Unfortunately, searching a case sensitive filesystem in a case insensitive manner is not practical.