I’ve not heard back from you, so hopefully the problem is no longer occurring. There are some changes in SpamSieve 3.2.2b2 that may resolve the issue. If not, please follow the instructions above to report more details about the message that’s triggering the problem.