Mojave Mail doesn’t like SpamSieve

[ChazMills]

@Michael_Tsai

Glad you figured it out. I will talk with the iLock developer and see whether there’s anything that can be done. Mail on Mojave is very sensitive about plug-in files not being touched/moved.

Maybe it installs something in the LaunchAgents folder?

SpamSieve installed in that folder but not iLock.

[joeg]

Me too!
I too have been having this problems since updating to Mojave. I followed all the instructions but every time I boot my iMac, SpamSieve tells me to make sure that the plugin is configured. It is! So, I click cancel and, as far as I can see, SpamSeive is working as it should - until I shut down - and then the Finder tells me that it can’t shut down because of SpamSieve! Annoying.

[Michael_Tsai]

@joeg

I too have been having this problems since updating to Mojave. I followed all the instructions but every time I boot my iMac, SpamSieve tells me to make sure that the plugin is configured.

Are you getting the dialog saying that SpamSieve disabled the rules, or only the one shown in your screenshot that says to enable the plug-in? The next time this happens, please send in a diagnostic report so that I can see why SpamSieve thinks the plug-in is not enabled.

@joeg

So, I click cancel and, as far as I can see, SpamSeive is working as it should

Do you see the SpamSieve commands in Mail’s Message menu?

@joeg

until I shut down - and then the Finder tells me that it can’t shut down because of SpamSieve!

I haven’t heard other reports of that happening. How long does it take if you try to quit SpamSieve yourself? This page describes how you can record what it’s doing so that we can see why it isn’t quitting.

[Michael_Tsai]

@joeg

I too have been having this problems since updating to Mojave. I followed all the instructions but every time I boot my iMac, SpamSieve tells me to make sure that the plugin is configured. It is! So, I click cancel and, as far as I can see, SpamSeive is working as it should - until I shut down - and then the Finder tells me that it can’t shut down because of SpamSieve!

Thanks for sending the report. The issue seems to be that you need to give SpamSieve Full Disk Access. (It looks like you had done this before, but somehow macOS forgot.)

I’m glad to hear that the problem quitting has not recurred.

[Michael_Tsai]

@joeg

I followed all the instructions but every time I boot my iMac, SpamSieve tells me to make sure that the plugin is configured. It is!

I made some changes in the SpamSieve 2.9.34b1 public beta that should help with this. It seems to be caused by Mail taking a long time to launch.

[ChazMills]

Gonna give the beta a try

@Michael_Tsai

I made some changes in the SpamSieve 2.9.34b1 public beta that should help with this. It seems to be caused by Mail taking a long time to launch.

I’m gonna give the beta a try.

[ChazMills]

Issue no more

@Michael_Tsai

I made some changes in the SpamSieve 2.9.34b1 public beta that should help with this. It seems to be caused by Mail taking a long time to launch.

After installing the latest public beta 2.9.34b1 and launching Mail a number of times, I have not experienced any further instances of SpamSieve alternatively activating/deactivating its Mail rule.

[Michael_Tsai]

@ChazMills

After installing the latest public beta 2.9.34b1 and launching Mail a number of times, I have not experienced any further instances of SpamSieve alternatively activating/deactivating its Mail rule.

Glad to hear it! Thanks for the follow-up.

[ChazMills]

Rule activation issue conditionally returns

@Michael_Tsai

Glad to hear it! Thanks for the follow-up.

When I was running SpamSieve public beta 2.9.34b1, I launched Apple Mail and had no problem with the rule activation/deactivation issue that I had experienced. With public beta 2.9.34b2, if I launch Apple Mail first, the issue occurs again. If I launch SpamSieve first then Apple Mail, the issue does not occur. In both cases, I had the third party app iLock enabled which requires me to enter a password before I can launch certain apps. It hasn’t taken any longer to enter the 7 character password under b2 than it did under b1.

[Michael_Tsai]

@ChazMills

With public beta 2.9.34b2, if I launch Apple Mail first, the issue occurs again. If I launch SpamSieve first then Apple Mail, the issue does not occur. In both cases, I had the third party app iLock enabled which requires me to enter a password before I can launch certain apps.

Please click this link to enable some debug logging. Then, the next time the problem occurs, send in a diagnostic report.

[ChazMills]

Must have just been a hiccup

@Michael_Tsai

Please click this link to enable some debug logging. Then, the next time the problem occurs, send in a diagnostic report.

The issue with the public beta 2.9.34b2 has not repeated itself even with my launching Mail. SpamSieve loads as expected and there have been no further incidents with the activation/deactivation of SpamSieve’s rules. Must have just been an isolated glitch.

[Michael_Tsai]

@joeg

I too have been having this problems since updating to Mojave. I followed all the instructions but every time I boot my iMac, SpamSieve tells me to make sure that the plugin is configured. It is!

This should be improved in SpamSieve 2.9.34b3.

[Michael_Tsai]

I made some more changes in the SpamSieve 2.9.35b1 public beta that should address a problem with SpamSieve erroneously disabling it Mail rule when its plug-in actually was loaded.