How do you tell if antispam's being updated?

[Baylink]

Is there something I can look for to see when SA rules are updated, and whether user-submitted examples are being processed?

I only have 55 reports in my spam mailbox, so I guess that's a good sign...

[uxbod]

SA rules do not automatically update within ZCS; you would need to manage that yourself. I am making the assumption that you mean from user supplied samples that is when they have been marked as Junk ? IMHO I wish Zimbra would move the Bayes to the MySQL instance so that it could be shared between mailstores and front-end MTAs.

Bug 18192 - use alternative database for SpamAssassin

[Baylink]

Well, I said "and" because I meant both, yes.

sa-update isn't run automatically, then?

[uxbod]

Even though ZCS now includes those tools it does not automagically update the rules

[uxbod]

Please vote for Bug 45913 - Spamassassin should update its rules.

[Baylink]

Ok. Or I can plug it in myself. Or just know I need to do it, which is often better.

But it is safe, on the other topic, for me to assume that user-submitted spam is removed from the spam-train mailbox when it's processed?

[Baylink]

And on the other side, since I gather SA is run from Amavisd, how does one get it to pick up newly updated rules? Does it happen automagically?

[ewilen]

Originally Posted by Baylink

But it is safe, on the other topic, for me to assume that user-submitted spam is removed from the spam-train mailbox when it's processed?

I used to see some weirdness here--it seemed like spam wasn't being cleared out of the spam/ham accounts. I associated this with the mail having a "read" flag, but I didn't investigate or test much. Just to be on the safe side, whenever I manually examine the spam/ham accounts, I make sure to leave all the mail in an "unread" state. (My thread on this: zmtrainsa --cleanup not fully cleaning up.) For all I know, if this ever was a bug, it may have been fixed by now.

Note that the documentation for zmtrainsa isn't complete. E.g., as called in crontab, it takes a flag --cleanup but this isn't mentioned the CLI documentation, and only alluded to in the antispam topic. In addition the docs don't make clear that it can be invoked without any arguments, as is done in zimbra crontab. Also, the zimbra crontab invokes sa-learn directly, along with zmtrainsa.

[Rich Graves]

After adding custom rules, run zmamavisdctl restart && postqueue -f. The latter catches any mail that was sent or received while amavisd was restarting.

This shouldn't be a frequent occurrence. sa-update is very stable, especially for 3.2, though you should run it after each ZCS install or upgrade. Until ZCS includes the just-released 3.3.1, possibly in 6.0.7, its stock 3.2.5 rules will be quite old. Zimbra has only patched critical things like y2k10; else, releases contain rules as of 2008.