Recent Releases

9/5/2008: Version 4.0.4

Bug fixes only for a compiler warning on 64-bit Linux systems and an error in the logging that was sending all messages to both the standard error and the system logs.

View the changelog
View the upgrade instructions
Download spamdyke 4.0.4

8/15/2008: Version 4.0.3

Bug fixes only for an integer parsing error on FreeBSD and incorrect handling of invalid nameservers in /etc/resolv.conf.

Download spamdyke 4.0.3

8/6/2008: Version 4.0.2

Bug fixes only for a graylist directory error that resulted in very deep directory structures for empty senders.

Download spamdyke 4.0.2

General Discussion Mailing List

For general discussion about spamdyke:

spamdyke-users@spamdyke.org

This list is the correct place to ask questions, make suggestions, report bugs or discuss anything else about spamdyke. Everyone can post and respond on this list.

List archives are available here:

spamdyke-users archives

Our archives are searchable thanks to mail-archive.com:

Search the archives

Release Announcements Mailing List

For release announcements only:

spamdyke-release@spamdyke.org

This list is only for broadcast announcements of new spamdyke releases. No posts are allowed from the subscribers. This list also sends its messages to the spamdyke-users list, so there is (normally) no reason to subscribe to both lists.

List archives are available here:

spamdyke-release archives

Our archives are searchable thanks to mail-archive.com:

Search the archives

Development Mailing List

For spamdyke developers and beta testers:

spamdyke-dev@spamdyke.org

This list is for developers and beta testers to discuss upcoming releases. This is not the correct place to offer feature suggestions; subscribe to spamdyke-users so everyone can read new ideas. Instead, this list is just for bug reports and troubleshooting for beta versions of spamdyke.

IMPORTANT: Anyone can subscribe to this list, but please do not install beta versions of spamdyke unless:

  1. You know what you're doing.
  2. You're willing to report bugs and successes (silent beta testers are worthless).
  3. You're able to install frequent updates/patches to troubleshoot problems.
  4. You're willing to risk losing some email.
  5. You're willing to risk upsetting some users.
  6. You have your employer's and users' permission.

List archives are available here:

spamdyke-dev archives

Our archives are searchable thanks to mail-archive.com:

Search the archives