Home | About Spam | About SpamBouncer | Downloads | Configuration | Reference | Resources
Overview | Quick Start | Preparation | Installation | Configuration | Troubleshooting | Bug Reports | Upgrading
A list of known SpamBouncer bugs, Procmail bugs, and other bugs that affect the SpamBouncer are discussed below. Workarounds are provided where possible. If you find a bug and a workaround, please notify the webmaster so that your fix can be provided for others.
The Procmail 3.22 "Recipe Header Flag Bug" is a bug that causes Procmail to get "stuck" after the first recipe in a session, ignoring subsequent header flags and treating all subsequent recipes as if they had the same header flags as the first. This especially affects recipes that specify what to search -- message header, message body, or both. This bug causes both false positives and false negatives (missed spam), and any amount of truly bizarre behavior.
The problem is caused by a buggy release of Procmail 3.22. Unfortunately, this buggy Procmail 3.22 release has been included as the default Procmail in several current Linux releases, the current OpenBSD release (which hit me), and probably other current Unix OS releases. So it is hitting a fairly substantial number of people.
If you have this bug, you can do one of three things to fix it:
If you can find and install a fixed release of Procmail 3.22, or roll your Procmail back to 3.15, I recommend that you do that. The bug in question is likely to affect your own Procmail recipes, not just the SpamBouncer. Writing Procmail recipes that the buggy release won't mishandle is a nuisance, and the resulting code is bulkier.
If your SpamBouncer does not appear to be filtering much spam, and you see the following line or something similar repeatedly in your Procmail log, you have this problem:
socket.c:1100: internal_send: 0.0.0.2#53: Invalid argument
This can be caused by several things. By far the most common is that you forgot to set SHELL=/bin/sh or to some other Bourne shell variant in the variables section of your .procmailrc file, and your default shell is c-shell or a variant. Both Procmail and at least some versions of the Unix host utility do not run well under c-shell or any shell based on c-shell. To fix this bug, set the SHELL variable properly in your .procmailrc file.
NOTE: If you base your .procmailrc on the sample procmail.rc file provided in your SpamBouncer distribution, in the auxiliary subdirectory, you will avoid mistakes like this one. 
If you have the SHELL variable set to a Bourne shell variant in your .procmailrc file, then the problem is either with your host program or with the DNS setup on your server. The system administrator will need to look into installing a working copy of host or fixing DNS.