Amavisd routinely fails to correctly tag Spam via SpamAssassin calls

[Quanah Gibson-Mount via amavis-users]

--On Monday, March 24, 2014 2:17 PM -0700 Quanah Gibson-Mount via 
amavis-users <amavis-users at amavis.org> wrote:


> *ANY* insight into how to debug why Amavis is utterly failing to scan
> obvious spam would be much appreciated.

Some interesting bits from the Amavis logs.  There is nothing from:

Mar 24 15:11:51 edge01 amavis[20181]: (20181-02) p001 1 Content-Type: 
text/plain, size: 2426 B, name:

to

Mar 24 15:11:55 edge01 amavis[20181]: (20181-02) spam-tag, 
<HealthWatch at go-smokeless-now.us> -> <quanah at zimbra.com>, No, score=0.743 
tagged_above=-10 required=3 tests=[BAYES_00=-0.05, RDNS_NONE=0.793] 
autolearn=no autolearn_force=no

Other than it took 4 seconds to get that far.

However, Amavis *fully processed* another email IN BETWEEN.  For that 
in-between email, it logged timing, both for SA and overall.

Mar 24 15:11:52 edge01 amavis[15252]: (15252-14) TIMING-SA [total 3885 ms, 
cpu 3692 ms]
Mar 24 15:11:52 edge01 amavis[15252]: (15252-14) size: 160473, TIMING 
[total 4159 ms, cpu 3798 ms, AM-cpu 106 ms, SA-cpu 3692 ms]

Neither of these bits is logged for the email that was not fully scanned. 
Possibly race condition or thread loss when processing multiple emails?

--Quanah

--

Quanah Gibson-Mount
Architect - Server
Zimbra, Inc.
--------------------
Zimbra ::  the leader in open source messaging and collaboration