zmtrainsa http get failed

[helpdesk_eforce]

hi,

I am using zcs 4.5.6 and suddenly this error is started on my server. due to this it create very big file of spamtrain.log. so please give anyone can provide the solution on this behalf. user account is already there using command to check spam user it is visible. so please let me know what to do.

bayes: synced databases from journal in 2 seconds: 1090 unique entries (2575 total entries)
[] INFO: Total messages processed: 0
[] INFO: Total messages processed: 0
[] INFO: Total messages processed: 0
[] INFO: Total messages processed: 0
Learned from 0 message(s) (0 message(s) examined).
Learned from 0 message(s) (0 message(s) examined).
bayes: synced databases from journal in 0 seconds: 150 unique entries (210 total entries)
[] INFO: Total messages processed: 0
[] INFO: Total messages processed: 0
[] WARN: exception occurred fetching message
java.io.IOException: HTTP GET failed: /service/user/spam.bxoa6zxa1@mail.eforceglobal.com/?id=951338d7-d2ca-4012-a137-edc552e3a144:265: 403: permission denied: you do not have sufficient permissions
at com.zimbra.cs.util.SpamExtract.extractMessage0(Spa mExtract.java:322)
at com.zimbra.cs.util.SpamExtract.extractMessage(Spam Extract.java:305)
at com.zimbra.cs.util.SpamExtract.extract(SpamExtract .java:254)
at com.zimbra.cs.util.SpamExtract.main(SpamExtract.ja va:202)
[] WARN: exception occurred fetching message

[jholder]

Hi eforce,
Please upgrade to 4.5.9, and let's see if that fixes the issue.

[helpdesk_eforce]

this is not the better solution. if i am going to upgrade then there is lots of issue.
1. user account information is simply migrate or not?
2. mbox data will work with 4.5.9 or not?
3. for upgrade if i am taking full backup, then stoping mta and strarting installation of 4.5.9, then if i am trying to restore my old full backup. is it works and my all employee of this company get them mail or not?
4. if during upgrade if i will get error then is there any possiblity to revert back to my old one zcs?

if anybody have perfact solution for my this error then give to us. to do upgrade is not solution. because in 4.5.6 this bug was solved and running fine. but after some time this was again created.

waiting for well response

[jholder]

Make a backup before you upgrade, and you should be fine.

[jholder]

Looks like you've opened a support case, which is great!

Hopefully support will be able to help you resolve this issue.