> To make matters worse, SpamAssassin's scores are reals and > UNIX's exit codes are ints. You just don't want to fiddle with > the exit code because you may need it for something else.
> Run messages through a default spamc to a temp file, grab the spam > score, and do with that what you want. Double-scanning is not the > answer, especially if you've got a busy site. Actually, I tried exactly this, and then sent a "normal heavy" load through my SpamAssassin script to test it, and there were times when the temp file would be overwritten before the current spamc process was done with it. I found you have to keep the data flowing (such as sequential pipes) otherwise you have to start locking files. I will keep working on a solution, but if anyone has any suggestions, please let me know.
