Package psi-plus-plugin-stopspam: Information

Binary package: psi-plus-plugin-stopspam
Version: 1.5.1494-alt1
Architecture: x86_64
Build time:  Apr 28, 2021, 06:48 PM in the task #270884
Source package: psi-plus
Report package bug
License: GPLv2
Summary: Stop spam support for psi-plus
Description: 
This plugin is designed to block spam messages and other unwanted information from Psi+ users.
The functionality of the plugin is based on the principle of "question - answer".
With the plugin settings you can:

 - Define a security question and the answer
 - Define the set of rules that define whether to the trigger plugin for a contact
 - Define the text messages sent in the case of the correct answer
 - Enable notification through popups
 - Enable the saving of blocked messages in the history of the contact
 - Define the number of subject parcels
 - Set the time interval after which to reset the number of how many questions will be sent
 - Enable blocking of private messages in conferences
 - Choose for which ranks and roles of conference participants blocking messages will be disabled
 - Enable deadlocks in private messages to participants who do not fall into the exceptions list for the roles and ranks which include blocking.

The rules are checked from top to bottom. If the rule is Enabled - stopspam is triggered, otherwise - stopspam is not triggered. In the case where none of the rules triggered stopspam for roster messages, you can specify whether the plugin will activate or not. For private messages from the same conference, it will always work.
Question and answer as well as a list of rules is common for ordinary messages and for private messages in conferences.
When a user has passed, the test will send a re-authorization request. It should be noted in the messages that are sent back the security question was correctly answered.
The plugin keeps a log of blocked messages, which you can view through the plugin settings.
The Reset button deletes the log and resets the counter of blocked messages.
WARNING!!! Before registering a new transport, it is recommended to add its jid to transport exceptions. This is due to the fact that after the transport registration, authorization requests for all contacts will be sent and if the transport was not added to as an exception, the plugin will block all the requests.

Maintainer: Oleg Solovyov


Last changed


April 28, 2021 Oleg Solovyov 1.5.1494-alt1
- Version 1.5.1494
Oct. 2, 2020 Oleg Solovyov 1.4.1513-alt1
- Version 1.4.1513
Oct. 16, 2019 Oleg Solovyov 1.4.912-alt1
- Version 1.4.912
- disabled QtWebKit (Closes: #37381)