Reply to thread

I've snipped out some of the details -- they won't be relevant to this error.

Though interestingly, I'm not totally sure why either of those would generate this error. Did looking at the spam trigger list create a new instance of the error you mentioned in the first message?