The current public beta version of SpamSieve has preliminary support for Apple Mail on macOS 11. You can sign up below to be notified when new beta versions are available and download them from within the app.
The beta release notes are available in the Software Update window and also in the “Version History” section of the manual (in the Help menu).
We do not recommend using a macOS beta on your main Mac, as there may be bugs that we have not had time to, or cannot, work around. With that said, we do welcome bug reports so that we can investigate any bugs and report them to Apple or try to develop workarounds. Please submit any feedback or bug reports via e-mail, rather than posting here.
Michael, Re your last email, think I figured out why the recommended method Manual 7.1.1.1 D(Manually Delete DataVaults) to access from Go To Folder: ~/Library/Containers/com.apple.mail/Data
If the system finds no file once, it tries to correct the next occurrence of part of that direction to something else that may exist (fix your typing?). Did not try turning off spelling correction, but it’s very frustrating. Your instruction line added to the online manual didn’t help.
Also frustrating (yes, Terminal was not set to Full Disk Access, which I fixed and retested)… Finding DataVaults Folder. You can set the EnableBundles OK and confirm by trying it a second time to get a nil file. However (7.1.1.1, Part C,5) the write command does no good. Back to Part D 6. Getting to the folder in the Go To Folder. Getting to the Folder that way to delete it fails because of the above anomaly in typing in the dialog box. Once wrong you can’t enter it again. In any event the file isn’t living there and the plug in still fails to install for me (SIP off).
Regarding the instructions in section 7.1.1.1, there are cases where “C. Ask Mail to Reset the DataVaults” is not enough and you need “D. Delete the DataVaults Folder.” In this case, I have found that it works to use the Go to Folder… command in Finder and type the path exactly. Do not use Tab auto-completion or Finder will change the path to something that doesn’t work. We confirmed in the e-mail that you sent me that your system did have the folder in question.
The other option is to delete the folder from Terminal by entering the command:
Yes. I did both, and it worked as documented in the email. However the end result, for me at least still wasn’t achieved. The Big Sur installation of SpamSieve mail bundle Plug-in still failed to activate. DataVaults was replaced when Mail reopened. I checked to see it removed and again with Terminal’s ls command on the the folder to see it replaced:
Beta 4 broke SpamSieve Plug-in version so 2.9.40b2 no longer works after MacOS upgrade. So far, I tried uninstall/reinstall of the Plug-in. I’ll try the remaining remedial steps when time permits. Just thought you’d like to know.
The latest version of Big Sur, Beta 5 causes a failure to the latest SpamSieve I’ve seen (2.9.40b3)! Is there an update? Beta 4 worked fine with this version. Apple has changed something. Screen Shot 2020-08-21 at 11.36.58|390x500
Of course you are, had no doubt whatsoever. Until I posted about the issue (and it was pinned), I did not see the other related postings. Sorry to bug you, it’s early on, but seems unusual they would crash what was already working fairly well.
Hi Michael. I am currently running MacOS Big Sur with the beta version of SpamSieve. I am currently having an issue where Spamsieve is flagged because the developer cannot be verified. I’ve uninstalle/reinstall SpamSieve and installed beta but the results are the same. I’ve attempted to turn SIP off / on but cannot locate the folders to delete and recreate the data vaults as listed in section 7.1.1.1. Right now I am running without Spamsieve (not a major problem) but wanted to let you know about the difficulties. I am also not sure if I should notify you directly or through Apple Beta Feedback Assistant.
