Great. I believe the underlying bug is fixed in SpamSieve 3.0.1b3 so that this won’t be necessary for other people.