C-Command Software Forum

El Captain Problem: Spam Messages Marked But Not Moved

I have been having the same experience after my El Capitan install. SpamSieve will properly identify and mark messages as spam (i’m color coding them) but will randomly stop moving them to the identified spam folders. Training an individual spam message works fine and does move them to proper folder. Here’s the latest console errors I’m seeing:

10/19/15 12:12:39.975 PM Mail[75018]: SpamSieve Mail Plug-In: Launching via launch agent failed.
10/19/15 12:12:43.284 PM Mail[75018]: SpamSieve Mail Plug-In: Error reading server port: <NSError Domain=NSCocoaErrorDomain Code=260 UserInfo={
    MJTStackFrames =     (
        "+[NSDictionary(MJTPropertyListSerialization) mjtReadURL:error:] (122)",
        "+[NSPropertyListSerialization(MJT) mjtPropertyListWithContentsOfURL:options:format:error:] (77)"
    );
    NSFilePath = "/Users/gary/Library/Mail/SpamSieve/ServerInfo.plist";
    NSLocalizedDescription = "The file \U201cServerInfo.plist\U201d couldn\U2019t be opened because there is no such file.";
    NSLocalizedFailureReason = "The file doesn\U2019t exist.";
    NSUnderlyingError = "<NSError Domain=NSPOSIXErrorDomain Code=2 UserInfo={
    NSLocalizedDescription = \"The operation couldn\\U2019t be completed. No such file or directory\";
    NSLocalizedFailureReason = \"No such file or directory\";
}>";
}>
10/19/15 12:12:49.000 PM kernel[0]: SpamSieve[75227] triggered unnest of range 0x7fff93800000->0x7fff93a00000 of DYLD shared region in VM map 0x910375b376ad1885. While not abnormal for debuggers, this increases system memory footprint until the target exits.

This does not sound like the same problem to me, because the original poster said that the spam messages were not marked. Please update to the latest public beta version (2.9.22b2) and also see the Why are messages marked as spam in Apple Mail but not moved? page. If you still see the problem, please contact me via e-mail with your Console log.

I did not hear back from the original poster, and this looks like an issue that was resolved in SpamSieve 2.9.23.