I have a couple of errors in the log file. One was caused by a specific facebook notification message that I would like to have as “not spam” (but I can’t find the message in the log), and the other is an error that I see occasionally (perhaps caused by the large size <35k messages> of the inbox ?). Any suggestions?
Is the “Predicted: Spam” log entry in your screenshot for the message in question? If not, I don’t think SpamSieve moved the message anywhere so there would be no need to train it.
The errors are probably not related to the number of messages that you have. SpamSieve is slowing down its requests because Mail seems to be overloaded. Perhaps you can see in its Activity window what it’s doing, though often it’s not clear. There are some basic tips to reduce the overhead in Mail, but usually the core issue seems to be a bug where Mail will try to redownload the message from the server even though it’s already cached locally.
Yes, it is. And, it was put in spam. I can train it as not spam, but from the the log details I’m afraid that SS won’t correctly recognize it.
I will review the link to reduce AppleMail overhead.
It looks like there may be an issue with your SpamSieve settings. Do you have Train SpamSieve blocklist unchecked?
And it’s odd that SpamSieve is not finding a Subject or From. Could you drag that log entry to Finder to export it and then send me the file?
I don’t see why it wouldn’t, but you could also train it from the Log window to make sure SpamSieve trains the exact same data that it used for the prediction.
No, all three are checked: Blocklist, Allowlist, and Bayesian.
Log entry dragged to Finder:
8Zqiltj9SkOAS53TJQyvng== (Predicted Spam (99)).eml|attachment (17.1 KB)
Hmm, OK. It looks like SpamSieve thought this message was spam because a long time ago you had trained it with a spam message that had no sender address, and this message had no sender address, and at no time in between were any good messages like that trained.
It seems that Mail gave SpamSieve incomplete data for this message, so all the header information was missing, even though it does seem to be stored in Mail now. Since the message datas differ, I recommend training the log entry in SpamSieve as good rather than training the message in Mail.
For intrest, I just saw that another message earlier yesterday had the same condition. Also sandwiched between similar errors. (not a message that I care about, though)
Interesting. I don’t know what would cause that. I can’t recall this ever happening for anyone else.
I wonder if you train the same message again from Mail if it would this time give SpamSieve all the message data.