This seems to have been caused by a bug in macOS Tahoe 26, and SpamSieve 3.2.2b1 includes a workaround that you can enable.
1 Like
This seems to have been caused by a bug in macOS Tahoe 26, and SpamSieve 3.2.2b1 includes a workaround that you can enable.