# Replies to discobot tutorial flagged as spam

**URL:** https://meta.discourse.org/t/replies-to-discobot-tutorial-flagged-as-spam/146399
**Category:** Support
**Created:** [April 1, 2020, 7:36am UTC](https://meta.discourse.org/t/replies-to-discobot-tutorial-flagged-as-spam/146399 "2020-04-01T07:36:50Z")
**Posts on this page:** 11
**Page:** 1

<div class="post-metadata">

### Author: ![agmontpetit](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/agmontpetit/32/160109_2.png) [@agmontpetit](https://meta.discourse.org/u/agmontpetit)
#### Post date: [April 1, 2020, 7:36am UTC](https://meta.discourse.org/t/replies-to-discobot-tutorial-flagged-as-spam/146399/1 "2020-04-01T07:36:50Z")

</div>

I’ve seen a couple of users signing up to our site and having their private messages with Discobot flagged by the system as _inappropriate_:

 ![Screen Shot 2020-04-01 at 09.25.43.png](https://global.discourse-cdn.com/meta/original/3X/e/b/ebfd4a1d66489cf5f77c0d481707e5871e24a633.png)

This is what appears in the _review_ section.

 ![Screen Shot 2020-04-01 at 09.29.52.png](https://global.discourse-cdn.com/meta/original/3X/c/5/c5342e09bb446d3d9167aa6d2aad412b9d71439d.png)

This is not ideal, as users get a bad impression from our site once they receive this message:

 ![Screen Shot 2020-04-01 at 09.36.29.png](https://global.discourse-cdn.com/meta/original/3X/9/4/94ce094766663192a48ee4e23394eca6dac3c857.png)

This happened to several messages from a couple of users while doing the discobot tutorial, which ends up being a terrible experience, especially for a newcomer.

I’ve checked this [post](https://meta.discourse.org/t/discobot-tutorial-flagged-as-spam/112731/3), but those users haven’t posted anything on our site yet (apart from replying to Discobot), so I don’t think changing the value of `newuser_spam_host_threshold ` is the solution.

Any ideas?

---

<div class="post-metadata">

### Author: ![simon](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/simon/32/339122_2.png) [@simon](https://meta.discourse.org/u/simon)
#### Post date: [April 1, 2020, 6:21pm UTC](https://meta.discourse.org/t/replies-to-discobot-tutorial-flagged-as-spam/146399/2 "2020-04-01T18:21:18Z")

</div>

> [@agmontpetit](#):
>
> I’ve seen a couple of users signing up to our site and having their private messages with Discobot flagged by the system as _inappropriate_ :

What version of Discourse is your site on?

Is there anything in common with the posts that have been flagged as inappropriate?

---

<div class="post-metadata">

### Author: ![agmontpetit](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/agmontpetit/32/160109_2.png) [@agmontpetit](https://meta.discourse.org/u/agmontpetit)
#### Post date: [April 1, 2020, 6:27pm UTC](https://meta.discourse.org/t/replies-to-discobot-tutorial-flagged-as-spam/146399/3 "2020-04-01T18:27:17Z")

</div>

> [@simon](#):
>
> What version of Discourse is your site on?

2.5.0.beta2 ([86690155b3](https://github.com/discourse/discourse/commits/86690155b3d619f0ad3c2d9e1991f9fbdbb3ff87))

> [@simon](#):
>
> Is there anything in common with the posts that have been flagged as inappropriate?

Reproduced the issue again with a different user. It seems any reply with an emoji triggers the system flag. This happens before `discobot` asks for a test flag.

 ![Screen Shot 2020-04-01 at 11.02.47.png](https://global.discourse-cdn.com/meta/original/3X/c/8/c8d488c85a1a6ab8d1101a141d4ee362a3cf3b01.png)

---

<div class="post-metadata">

### Author: ![codinghorror](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/codinghorror/32/110067_2.png) [@codinghorror](https://meta.discourse.org/u/codinghorror)
#### Post date: [April 2, 2020, 4:20pm UTC](https://meta.discourse.org/t/replies-to-discobot-tutorial-flagged-as-spam/146399/4 "2020-04-02T16:20:59Z")

</div>

Unless you can reproduce it here or on [try.discourse.org](http://try.discourse.org), this is due to unusual settings on your instance.

---

<div class="post-metadata">

### Author: ![pfaffman](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/pfaffman/32/120154_2.png) [@pfaffman](https://meta.discourse.org/u/pfaffman)
#### Post date: [April 7, 2020, 5:02pm UTC](https://meta.discourse.org/t/replies-to-discobot-tutorial-flagged-as-spam/146399/5 "2020-04-07T17:02:57Z")

</div>

> [@simon](#):
>
> Is there anything in common with the posts that have been flagged as inappropriate?

Not that I can find. A recent new user got flagged for both his emoji post as well as the onebox post, so it doesn’t appear to be related to content. Akismet isn’t installed. It happens for multiple IPs. It seems to happen only with new users? Posts are flagged with 63% badness consistently and the user gets

> [@](#):
>
> Your post was flagged as **inappropriate** : the community feels it is offensive, abusive, or a violation of [our community guidelines](https://www.pricemate.com/guidelines).

In addition to Topic List Previews and a custom plugin that doesn’t look suspect to my naive eye. I don’t see in the logs where the posts are getting flagged, so I’m not sure where else to look for an explanation. What are the things that can trigger a post to get auto-flagged? Where else can we look?

---

<div class="post-metadata">

### Author: ![codinghorror](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/codinghorror/32/110067_2.png) [@codinghorror](https://meta.discourse.org/u/codinghorror)
#### Post date: [April 7, 2020, 8:51pm UTC](https://meta.discourse.org/t/replies-to-discobot-tutorial-flagged-as-spam/146399/6 "2020-04-07T20:51:42Z")

</div>

So you can’t reproduce it on [try.discourse.org](http://try.discourse.org)?

---

<div class="post-metadata">

### Author: ![pfaffman](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/pfaffman/32/120154_2.png) [@pfaffman](https://meta.discourse.org/u/pfaffman)
#### Post date: [April 7, 2020, 9:19pm UTC](https://meta.discourse.org/t/replies-to-discobot-tutorial-flagged-as-spam/146399/7 "2020-04-07T21:19:36Z")

</div>

> [@codinghorror](#):
>
> So you can’t reproduce it on [try.discourse.org](http://try.discourse.org)?

That’s correct.

And I can’t reproduce it on the broken site with an existing admin user. It seems to have something to do with it being a new user. Maybe it’s breaking because they’re TL0? But that doesn’t make much sense.

> [@codinghorror](#):
>
> this is due to unusual settings on your instance.

I’ve looked at all of the non-default settings and see none that seem likely to cause this problem.

Right now the only solution that I have is “delete your forum and start over again” or maybe “reset all of your settings to their defaults.” (I will first remove the two plugins, but they seem like unlikely culprits. I guess I’ll try that as soon as it’s not too disruptive to the community.) I’m asking for some ideas of what I can try next to determine what’s causing this.

---

<div class="post-metadata">

### Author: ![codinghorror](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/codinghorror/32/110067_2.png) [@codinghorror](https://meta.discourse.org/u/codinghorror)
#### Post date: [April 7, 2020, 9:47pm UTC](https://meta.discourse.org/t/replies-to-discobot-tutorial-flagged-as-spam/146399/8 "2020-04-07T21:47:38Z")

</div>

There is a site setting which, when triggered with matching text, sends a post immediately to the flag queue based on that matching text (regex). Sam added that in the bamwar fighting days as I recall, and we used korean character sets as an immediate trigger for example? Because those never appear here (and I believe it is checked for new / TL0 users only, thus fairly safe).

That’s all I can think of.

edit: or watched words, would be the same thing..

---

<div class="post-metadata">

### Author: ![pfaffman](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/pfaffman/32/120154_2.png) [@pfaffman](https://meta.discourse.org/u/pfaffman)
#### Post date: [April 7, 2020, 9:56pm UTC](https://meta.discourse.org/t/replies-to-discobot-tutorial-flagged-as-spam/146399/9 "2020-04-07T21:56:56Z")

</div>

Searching . . . . Maybe you’re talking about `auto silence first post regex`?

> [@](#):
>
> Case insensitive regex that if passed will cause first post by user to be silenced and sent to approval queue. Example: raging|a[bc]a , will cause all posts containing raging or aba or aca to be silenced on first. Only applies to first post.

That sounds just like what I’m looking for! Alas, that ain’t it. 😿

---

<div class="post-metadata">

### Author: ![domr109](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/domr109/32/160246_2.png) [@domr109](https://meta.discourse.org/u/domr109)
#### Post date: [May 5, 2020, 6:09pm UTC](https://meta.discourse.org/t/replies-to-discobot-tutorial-flagged-as-spam/146399/10 "2020-05-05T18:09:53Z")

</div>

Good news, we were able to find the root cause of this issue.

Actually @pfaffman was reviewing our site settings and found out that we had changed a few default settings that had caused the issue.

For other users who might have this issue we had added several words to the Flag admin setting `admin/logs/watched_words/action/flag` including our own brandname `pricemate` along a few others.

 ![Screen Shot on 2020-05-05 at 19-06-05](https://global.discourse-cdn.com/meta/original/3X/1/0/10f28f8b648571045cf28cd15b5db8a160168a20.png)

We also changed settings like `min post length` among a few others to a very low value which could have also caused some issues. After removing those words and reverting the `Posting` settings to their default values the issue disappeared.

Kudos again to @pfaffman and thanks for helping us with this!

---

<div class="post-metadata">

### Author: ![system](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/system/32/443519_2.png) [@system](https://meta.discourse.org/u/system)
#### Post date: [July 3, 2024, 10:58pm UTC](https://meta.discourse.org/t/replies-to-discobot-tutorial-flagged-as-spam/146399/12 "2024-07-03T22:58:47Z")

</div>

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.
