prosody-modules
c0cb43817b7c
mod_report_tracker/README.markdown
Software / code / prosody-modules
File
mod_report_tracker/README.markdown @ 6113:c0cb43817b7c
mod_compliance_latest: using module:log_status
diff --git a/mod_compliance_latest/mod_compliance_latest.lua b/mod_compliance_latest/mod_compliance_latest.lua
--- a/mod_compliance_latest/mod_compliance_latest.lua
+++ b/mod_compliance_latest/mod_compliance_latest.lua
@@ -1,6 +1,6 @@
local success, err = pcall(function() module:depends("compliance_2023") end)
if not success then
- module:log("error", "Error, can't load module: mod_compliance_2023. Is this module downloaded in a folder readable by prosody?")
- return 1, "Error: Couldn't load dependency mod_compliance_2023."
+module:log_status( "error", "Error, can't load module: mod_compliance_2023. Is this module downloaded into a folder readable by prosody?" )
+return false
end
| author | Menel <menel@snikket.de> |
|---|---|
| date | Mon, 23 Dec 2024 14:09:56 +0100 |
| parent | 6063:b04518fa0987 |
line wrap: on
line source
--- labels: - 'Stage-Alpha' summary: 'Track abuse/spam reports from remote servers' --- This module tracks reports received from remote servers about local user accounts. The count of reports and the servers they came from is stored for inspection by the admin or for use by other modules which might take action against the reported accounts. ## Configuration ### Trusted reporters You can configure which servers the module will trust reports from: ``` trusted_reporters = { "example.com", "example.net" } ``` Reports from non-domain JIDs are currently always ignored (even if listed). Reports from domain JIDs which are not listed here are logged so the admin can decide whether to add them to the configured list. ## Compatibility Should work with 0.12, but has not been tested. Tested with trunk (2024-11-22).
