There’s a change in SpamSieve 3.0.3b1 that should work around the macOS bug that can cause this problem.