File

mod_onhold/README.markdown @ 4188:4611999fd8d3

mod_muc_batched_probe: don't rely on mt_room:respond_to_probe method That method assumes it's responding to a `<presence>` stanza, which breaks for the bached probe use-case.
author JC Brand <jc@opkode.com>
date Mon, 12 Oct 2020 13:21:16 +0200
parent 1803:4d73a1a6ba68
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.