-
Суть проблемы - бот с какого-то момента выдает бан всем подряд новым участникам за любой пост. stop-words.txt
Пользователя вручную разбанил, сейчас бот отключен. Если бота запустить, он удалит ВСЕ посты и забанит юзера снова. UPD: by @umputun - translation The essence of the problem is that the bot, at some point, starts issuing bans to all new members indiscriminately for any post. |
Beta Was this translation helpful? Give feedback.
Replies: 4 comments 3 replies
-
what exactly are you running? I mean, dockerized or binary and what version? Are you sure this is even tg-spam? The logs your provided look odd, as tg-spam doesn't have structural logs. This is what valid logs look like (with
This is not how tg-spam bot is working, it doesn't remove messages retroactively, but only reacts on new messages. So, let me repeat my question - are you sure you are running tg-spam bot? |
Beta Was this translation helpful? Give feedback.
-
if the log you gave is from the log file, this is not what we need to investigate the issue. I would like to see logs from the docker (or the binary) and better with pls note: stop-words.txt is not the only reason to ban, you also may have samples with the spam/ham dataset. |
Beta Was this translation helpful? Give feedback.
-
I'm running binary, version 1.13.2
I don't have any other bot, so yes )
I checked twice, downloaded the binary again and verified it, so yes
ok, but I wouldn't like to publish the log here - there's a lot of private information. Can I send it by mail or telegram? |
Beta Was this translation helpful? Give feedback.
-
sure, feel free to send it to my tg (same user name as here)
hard to say, but in theory if you have no ham/spam samples (they are pre-populated in docker version, but you may have not copied them or made them manually) and started to make spam samples manually, the classifier without any ham samples could detect messages that remotely resemble the spam sample as new spam. By the way, you can see in the logs what exactly triggered spam detection, check for "ban initiated for" messages and see "check results" in this line, i.e.
You will see one or more checks with As of now, I don't really see any bug to fix, but suspecting configuration issue of some sort. Will convert this issue to a discussion in FAQ section |
Beta Was this translation helpful? Give feedback.
sure, feel free to send it to my tg (same user name as here)
hard to say, but in theory if you have no ham/spam samples (they are pre-populated in docker version, but you may have not copied them or made them manually) and started to make spam samples manually, the classifier without any ham samples could detect messages that remotely resemble the spam sample as new spam. By the way, you can see in the logs what exactly triggered spam detection, check for "ban initiated for" messages and see "check results" in this line, i.e.