In trying to find out where my free disk space is going, I stumbled on some unusual behavior with SS 3.1.3. Using DaisyDisk, I discovered that the SS Log folder (~/Library/Application Support/SpamSieve/Log.spamsieve-logd/) has grown to over 150GB in size. I admit that I don’t know what it ‘usually’ is, but that seems like a LOT
When I look at SS’s log, it seems that every now and again SS gets caught in some kind of loop. The primary example seems to be a message that is still in one of my mailboxes (on an Exchange server). There are 12,389 (and counting) entries about this single message.
Scrolling back in the log, it appears this has happened before, but not to this degree.
I haven’t yet dealt with the specific email message (it’s still unread in my inbox), nor the thousands of log entries in case anyone has thoughts–or if Michael wants me to investigate anything.
It would help if you could select a few of those Predicted log entries, hold down the Command+ Control+Option+Shift keys, and choose Edit ‣ Copy Debug Info. Then paste the results into an e-mail or private message. Then I can investigate why there’s a loop. I wonder if something else is touching the message on the server such that Mail keeps seeing it as a different message.
Marking the message as read should get SpamSieve to stop checking it at all.
Once done troubleshooting, you can use the Prune full message data in log option in the settings to have SpamSieve auto-delete old message data, which is what’s probably using the bulk of the storage.
Email sent. Included some example from this latest loop as well as a couple of others I pulled up.
Marking the looping message as read has indeed stopped the loop. This specific message has been sitting in my inbox for so many days because I’ve been lucky enough to be on holiday!
Thanks for the reminder to check my prune settings. I do have “Prune full message data” turned on for the default of 30 days.
Not to hijack my own thread, but when using the “Search” box in the log window, what field(s) and log entries are being searched? For example, I tried entering “Pruned” into the search field, but no results were returned despite many entries in the log having “Type”=“Pruned” with their subject including the word too.
You could set it to prune after fewer days if you want to get rid of that looping data earlier, or (after we finish troubleshooting) you could select the log entries and manually delete them.
It searches the contents of the message (subject, message ID, sender, recipient, any key words that SpamSieve identified) but not the localized, SpamSieve-generated text.
