Mercurial > prosody-modules
comparison mod_onhold/README.markdown @ 1803:4d73a1a6ba68
Convert all wiki pages to Markdown
author | Kim Alvefur <zash@zash.se> |
---|---|
date | Fri, 28 Aug 2015 18:03:58 +0200 |
parents | mod_onhold/README.wiki@29f3d6b7ad16 |
children |
comparison
equal
deleted
inserted
replaced
1802:0ab737feada6 | 1803:4d73a1a6ba68 |
---|---|
1 --- | |
2 labels: | |
3 summary: 'Module enabling "on-hold" functionality' | |
4 ... | |
5 | |
6 Introduction | |
7 ============ | |
8 | |
9 Enable mod\_onhold to allow temporarily placing messages from particular | |
10 JIDs "on hold" -- i.e. store them, but do not deliver them until the | |
11 hold status is taken away. | |
12 | |
13 Details | |
14 ======= | |
15 | |
16 Right now, it is configured through adding JIDs to a list in | |
17 prosody.cfg.lua. Eventually, more dynamically configurable support will | |
18 be added (i.e. with ad-hoc commands or some such thing). | |
19 | |
20 Simply enable mod\_onhold in your list of modules, and then add a line: | |
21 | |
22 onhold\_jids = { "someone@address.com", "someoneelse@address2.com" } | |
23 | |
24 Until those JIDs are removed, messages from those JIDs will not be | |
25 delivered. Once they are removed and prosody is restarted, they will be | |
26 delivered the next time the user to which they are directed logs on. |