3.2 update broke everything

SpamSieve
, , , , ,
16

It looks like the main problem is that it’s taking a really long time for SpamSieve to read its corpus data from disk. As I said, this is probably related to your Mac using a slow hard drive instead of an SSD, but it’s unclear to me why the problem is only occurring now. Nothing about the way this works has changed in SpamSieve 3.2 (or even recently). Did you recently train it with a large number of messages so that there’s a lot more data than before?

Anyway, the two ways to fix this are:

  • You could try to defragment the current corpus on disk. macOS does not have a built-in command to do this, but one technique you could use is:

    1. Quit SpamSieve and Mail.
    2. Open the folder /Users/<username>/Library/Application Support/SpamSieve/Corpus.spamsieve-corpus.
    3. Select the Words.spamsieve-words folder and choose File ‣ Compress. This will create a Words.spamsieve-words.zip file.
    4. Drag the Words.spamsieve-words folder to the trash.
    5. Open the Words.spamsieve-words.zip file. This will create a new Words.spamsieve-words folder.
    6. Drag the Words.spamsieve-words.zip file to the trash.

It’s also possible that there’s a hardware problem with your Mac’s storage, unrelated to the SpamSieve data.

I also recommend updating to the SpamSieve 3.2.1 beta, as this includes more diagnostics.