managing false spam with ZCO

[mertz]

Hello,

Just a simple question:

How should proceed a user with emails falsely detected as spam when using outlook and ZCO?
Is it enough to delete or to move the false-spam from the spam folder?

This seems not be described in ZCO use rmanual (may be a doc bug?)

christophe

[phoenix]

Originally Posted by mertz

How should proceed a user with emails falsely detected as spam when using outlook and ZCO?
Is it enough to delete or to move the false-spam from the spam folder?

The answer to that would depend on the version of Zimbra and Z|CO you're using. Please update your forum profile with the output of the following command (do not post the output in this thread):

zmcontrol -v

[mertz]

thx,

done on my profile (in short: 6.04 on ubuntu)

christophe

[Rich Graves]

In versions later than 5.0.11 or so, moving the item to inbox will train the antispam system. You should do that. You can then delete or file the message elsewhere. (What it's done in the background is forwarded the message as an attachment to the system ham-XXXXX account.)

View->Toolbars->Zimbra Support->Show Original will display the X-Spam headers, possibly giving some hint what's going on. If the score is above 8, then bayes training is not going to be enough. The 6.0.4 web client added per-user sender whitelists in Preferences->Mail->Junk Mail Options.

[mertz]

thx for these infos specially on ZCO ....

BTW, I detected a bug with spamassassin (delivered with zimbra). The FH_DATE_PAST_20XX rule seems buggy since 2010 according to others such as : Spamassassin FH_DATE_PAST_20XX test buggy in 2010

I report a bug in zimbra bugzilla : Bug 44041 – spamassasin rule FH_DATE_PAST_20XX is broken in spamassassin


christophe

[phoenix]

Originally Posted by mertz

BTW, I detected a bug with spamassassin (delivered with zimbra). The FH_DATE_PAST_20XX rule seems buggy since 2010 according to others such as : Spamassassin FH_DATE_PAST_20XX test buggy in 2010

That's already been reported: [SOLVED] FH_DATE_PAST_20XX - Spamassassin bug - incorrect tagging from Jan 1, 2010 on