why aren't these spam messages going to the Junk folder? (4.5.1)

[shaver]

I just upgraded to 4.5.1, which went smoothly enough, but now things that are apparently detected as being spam are ending up in my inbox.

Example headers:

X-DSPAM-Result: Spam
X-DSPAM-Confidence: 0.9997
X-DSPAM-Probability: 1.0000
X-DSPAM-Signature: 45cc90a582151385515324
X-DSPAM-Factors: 15,
X-Virus-Scanned: amavisd-new at 
X-Amavis-Alert: BAD HEADER, Non-encoded 8-bit data (char AC hex): Date:
	\254P\264\301\244\255, 09 \244G\244\353 ...
X-Spam-Flag: YES
X-Spam-Score: 7.424
X-Spam-Level: *******
X-Spam-Status: Yes, score=7.424 tagged_above=-10 required=4
	tests=[BAYES_99=3.5, DNS_FROM_AHBL_RHSBL=0.231, DSPAM_SPAM=1.5,
	INVALID_DATE=2.193]

X-Virus-Scanned: amavisd-new at 
X-Spam-Flag: YES
X-Spam-Score: 10.312
X-Spam-Level: **********
X-Spam-Status: Yes, score=10.312 tagged_above=-10 required=4
	tests=[BAD_ENC_HEADER=3.1, BAYES_99=3.5, DNS_FROM_AHBL_RHSBL=0.231,
	HTML_IMAGE_ONLY_24=1.841, HTML_MESSAGE=0.001, URIBL_SBL=1.639]

Spam checking is turned on in the console, tag and kill %ages look right (20/75), and it's clearly detecting them as spam -- why are they ending up in my inbox instead of my Junk folder?

Mike

[shaver]

I just upgraded to 4.5.1, which went smoothly enough, but now things that are apparently detected as being spam are ending up in my inbox.

Still happening, starting to drown a bit in spam! Can anyone point me at the part of the system that usually puts Spam-Flag: YES stuff into the Junk folder? I'm trying to find it in my zimbra config to make sure it's still set correctly, but I'm having an unfortunately small amount of luck right now.

Mike

[jholder]

Hi Shaver,
Sorry to hear your trouble with spam!

Please run the following command:
zmprov gacf | grep -i spamis

and verify the accounts exist.

Thanks
john

[shaver]

Hi Shaver,
Sorry to hear your trouble with spam!

Please run the following command:
zmprov gacf | grep -i spamis

and verify the accounts exist.

Thanks
john

Indeed, the spam stuff turned out to be working for all the other users on my system, so I started comparing filter rules. I have a rule that forwards mail to my blackberry, but I want to keep a copy in my INBOX as well. To that end, I picked "Keep in inbox" as my last option -- without it I was _only_ getting mail forwarded to the device -- which, I discovered by reading ZimbraMailAdapter.java, means that the spam flag isn't checked at all!

I ended up adding an explicit test in my rule for X-Spam-Flag: YES, and now I think I'll get the behaviour I want. Certainly a surprising outcome, especially if you know that the spam flagging has already happened when the SIEVE rules are run!

Mike

[jholder]

Good thinking. Keep in mind however, you've only treating the symptom. Now, what/where's the problem.

[shaver]

Good thinking. Keep in mind however, you've only treating the symptom. Now, what/where's the problem.

No, that was the real problem. My filter rules were causing the spam filtering in ZimbraMailAdapter to be skipped, so even if the header was being set correctly by SA, it wasn't affecting the disposition of the messages.

Once I made my rule painfully explicit about the fact that it shouldn't be called for X-Spam-Flag: YES, I no longer hit the "keep in inbox" action in that case. This means that X-S-F: YES messages go the implicit-keep route in ZimbraMailAdapter, and all is well.

(If somewhat confusing. )

Mike