Zimbra Forums

Thank you Gentlemen,
That seems to have been the issue and the train commands now run to completion.
Still having issues tracking down the corrupt message that breaks the cleanup command but progress !
Thanks again

tony

So if the spam account has less than 27 messages the spam training and cleanup works ?
When you say "manually", do you mean message by message ?
Thanks

Anyone ?
I have a 2nd thread on an adjacent subject
http://www.zimbra.com/forums/administra ... rrors.html
They seem related, anyone have any thoughts as to what the underlying issue might be ?
Thanks in advance

Am getting lots of errors in my spamtrain log, excerpt below. Anyone have a hint as to what might be causing the exception ? Bad message ? Bad index of some sort ? Training Snapshot: zimbra TP: 50 TN: 29 FP: 1 FN: 1 SC: 0 NC: 0 SHR: 98.04% HSR: 3.33% OCA: 97.53% Overall Statistics: zimbra TP: 499 TN...

Can anyone provide guidance as to what the service is that is unavailable for the spam extract process ?
Thanks

Thats an interesting suggestion, is that the Microsoft, take 2 reboots and call me in the morning approach ?
I am not using either proxy or memcached
Regards

Oh, my apologies, you're correct, 8.01 to 8.02.
Though, to be honest, I'm not sure these errors/issues are tied to the specific update.
Anecdotaly, they are more related to the 8.x update.
Regards

tony

So, like a few others, I have noticed an increase in Spam arriving at the Inbox since the 8.03 update. Investigation shows that errors are getting thrown by zmtrainsa and that Junk folders aren't being cleaned up. Error thread is below, any thoughts/opinions on what might be causing the error welcom...

I have just discovered I have the same problem, everything seems to be getting tagged higher than it was before.
Was there any adjustments in 4.5.7 ?

[quote user="17224bobby"]you may not see enough in the logs until you enable extra logging for pop and imap: in the file /opt/zimbra/conf/log4j.properties add one or both of these: log4j.logger.zimbra.pop=DEBUG log4j.logger.zimbra.imap=DEBUG right after this line*: log4j.logger.zimbra=ERRO...