If you're running SA 3.2.3 or higher, there were some new exit codes added that the Domino Spamassassin code doesn't know about. To fix it on my server, I opened my mail template (mail85.ntf) in the Domino designer, opened the SpamAssassin script library and edited the "mlngRunSpamAssassin" function.



Scroll all the way down to the bottom and find this section:

Loop Until blnRanSpamAssassin<br/>
mlngRunSpamAssassin = lngExitCode   <br/>
Exit Function<br/>

Add this line right under the Loop - "If lngExitCode > 1 Then lngExitCode=1"



The modified section of the function should look like this:

Loop Until blnRanSpamAssassin<br/>
If lngExitCode &gt; 1 Then lngExitCode=1<br/>
mlngRunSpamAssassin = lngExitCode   <br/>
Exit Function<br/>

That should fix it for you.



-=Phil

Hello, I fixed the same issue on my Linux server, and might be the solution for you. I enabled Spamassassin debug, and all the messages that had

X-SPAM-FLAG: YES

X-SPAM-LEVEL: *

X-SPAM-STATUS: Yes, score=13.1 required=5.0 tests=AWL,BAYES_99,

ham identified



It must be a case sensitive issue with Linux, after modifying the Script Libraries –> Spamassassin –> mHandleSpamOrHam



I changed this line from:

And (Instr(1, vstrSpamAssassinOutput, "X-Spam-Flag: YES", 1) > 0) Then

to

And (Instr(1, vstrSpamAssassinOutput, "X-SPAM-FLAG: YES", 1) > 0) Then



Now it is detecting spam properly:

X-SPAM-FLAG: YES

X-SPAM-X-SPAM-STATUS: Yes, score=14.8 required=5.0 t

spam identified