I believe the workaround in SpamSieve 3.2.1b1 fixes the problem, but please let us know here if you are seeing otherwise.