Software /
code /
prosody-modules
File
mod_onhold/README.md @ 6150:f77f5e408d6a
mod_sasl2_fast: Restore non-FAST SASL handler upon reset
This fixes an issue where, after failed FAST authentication, the FAST handler
was still used (even though the client now wants to try with a password or
other non-FAST credentials).
A little hacky perhaps, but probably the best we can do without baking FAST
support directly into mod_sasl2.
author | Matthew Wild <mwild1@gmail.com> |
---|---|
date | Thu, 16 Jan 2025 15:46:15 +0000 |
parent | 6003:fe081789f7b5 |
line wrap: on
line source
--- labels: summary: 'Module enabling "on-hold" functionality' ... Introduction ============ Enable mod\_onhold to allow temporarily placing messages from particular JIDs "on hold" -- i.e. store them, but do not deliver them until the hold status is taken away. Details ======= Right now, it is configured through adding JIDs to a list in prosody.cfg.lua. Eventually, more dynamically configurable support will be added (i.e. with ad-hoc commands or some such thing). Simply enable mod\_onhold in your list of modules, and then add a line: onhold\_jids = { "someone@address.com", "someoneelse@address2.com" } Until those JIDs are removed, messages from those JIDs will not be delivered. Once they are removed and prosody is restarted, they will be delivered the next time the user to which they are directed logs on.