SpamSieve times out/fails at every request to Apple Mail for days?

Hi,

I run SpamSieve with Apple Mail on a Mac mini i don’t look at much. As far as I can tell, it has been generating an error message on every single request of Apple Mail for days.

I tried restarting Mail (twice) but it didn’t make a difference. However, when I restarted SpamSieve, it started working again.

The latest error shown above (-1728 aka errAENoSuchObject) happened after restarting, was less common and I don’t think it is related. The “connection is invalid” messages errors were when I restarted Mail, which makes sense.

Is this behavior you’ve seen before? Is there any notification mechanism available so I don’t have to watch the log (or notice unfiltered spam) to see when there are failures for days?

The only recent change I can think of is that I updated an IMAP server (the “sabi.net” one), so Mail may have been busier redownloading email for a bit there. It’s entirely possible this issue will not recur as updating a mail server is not something I do every day!

Thanks.

I don’t think I’ve ever seen that before. Over the last few months, I’ve seen issues where Mail stops responding to AppleScript commands when it gets overloaded (e.g. syncing lots of messages), but not for hours or days on end.

If you launch SpamSieve before launching Mail, it’s more likely that the Mail extension will work and so SpamSieve will be able to filter the inbox even if it’s encountering AppleScript errors from Mail.

If you find that this happens again and that restarting SpamSieve seems to help, please let me know and maybe we can develop a better workaround.

I restarted Mail one last time just in case so it can use the extension. If this happens again is there anything you’d want to help isolate it (I realize this is a hard question to answer when the issue is unknown)?

Perhaps an Activity Monitor sample from Mail. I’ll see if I can think of anything else or any extra debug logging that I could add.

1 Like