misskat: A lemur trying to eat a lot of watermelon. lemur labeled as me, and the watermelon labeled as "everyone in this bar." (I love everyone in this bar)
[personal profile] misskat posting in [site community profile] dw_support_training
We've got a request about emailed comments bouncing back with the error "Client error: Message looks like spam." The user also gets a captcha when they go to the page to reply. Is anyone else getting this issue? Any ideas on what could be causing it?

K

Date: 2013-09-04 06:28 pm (UTC)
azurelunatic: Vivid pink Alaskan wild rose. (Default)
From: [personal profile] azurelunatic
My first thought is that perhaps the journal owner/community maintainer has voluntarily turned on the require-captcha requirement, or that it has incidentally turned on due to high comment volume.

My thought is further that the bounceback is the symptom of the captcha requirement, and that it may do this any time it hits that.

Date: 2013-09-04 08:24 pm (UTC)
denise: Image: Me, facing away from camera, on top of the Castel Sant'Angelo in Rome (Default)
From: [staff profile] denise
That's the protocol error for when the comment contains text that's included in our list of "phrases that are highly indiciative of spam". I did not think we had anything in that config item (and a quick look at the configs that are actually in use seems to agree with me) so something else is probably triggering it, even though I can't figure out what it is. Best guess is that's the error used when the journal owner has turned on captcha, since you can't solve a captcha through email.