|
1782
|
1 #summary XEP-0136: Message Archiving
|
|
|
2 #labels Stage-Unsupported
|
|
|
3
|
|
|
4 ----
|
|
|
5 This page is held here for reference only. mod_archive is no longer supported.
|
|
|
6
|
|
|
7 Similar modules:
|
|
|
8
|
|
|
9 * [mod_mam]
|
|
|
10 * [mod_mam_sql]
|
|
|
11 * [http://prosody.im/files/mod_log_messages.lua mod_log_messages] (mainly useful as a template for people making their own logging module)
|
|
|
12
|
|
|
13 *Note:* If you are an administrator looking for a module just for centrally logging messages passing to/from users on your server, this probably isn't the module you are looking for (mod_archive is for user-managed archives). We'd really like to hear about your requirements to make a module more tailored to this kind of use-case though (especially how/where you would like the messages stored)... drop us an email at developers@prosody.im to let us know.
|
|
|
14
|
|
|
15 ----
|
|
|
16
|
|
|
17 = Introduction =
|
|
|
18
|
|
|
19 Currently many XMPP clients save the messages locally and it's not convenient or even possible to retrieve the historical messages, especially when one switches the clients a lot.
|
|
|
20
|
|
|
21 = Details =
|
|
|
22
|
|
|
23 This module keeps an archive of incoming and outgoing messages for each user on the server, and allows the user to query and manage this archive using the XMPP extension described in [http://xmpp.org/extensions/xep-0136.html XEP-0136: Message Archiving].
|
|
|
24
|
|
|
25 *Note:* If you are an administrator looking for a module just for centrally logging messages passing to/from users on your server, this probably isn't the module you are looking for (mod_archive is for user-managed archives). We'd really like to hear about your requirements to make a module more tailored to this kind of use-case though (especially how/where you would like the messages stored)... drop us an email at developers@prosody.im to let us know.
|
|
|
26
|
|
|
27 = Usage =
|
|
|
28
|
|
|
29 First copy the module to the prosody plugins directory.
|
|
|
30
|
|
|
31 Then add "archive" to your modules_enabled list:
|
|
|
32 {{{
|
|
|
33 modules_enabled = {
|
|
|
34 -- ...
|
|
|
35 "privacy",
|
|
|
36 "archive",
|
|
|
37 -- ...
|
|
|
38 }}}
|
|
|
39
|
|
|
40 = Configuration =
|
|
|
41 || *Name* || *Description* || *Type* || *Default value* ||
|
|
|
42 || default_max || the maximum number of items to return when requesting collection list or archived messages || integer || 100 ||
|
|
|
43 || force_archiving || archive every message automatically, and do NOT consider the preferences || boolean || false ||
|
|
|
44 || auto_archiving_enabled || applied when no any preferences available || boolean || true ||
|
|
|
45
|
|
|
46
|
|
|
47 = Compatibility =
|
|
|
48 || 0.7.0 || Works ||
|
|
|
49
|
|
|
50 = TODO =
|
|
|
51 * consider '`exactmatch`' attribute when do JID matching.
|
|
|
52 * return a `<feature-not-implemented/>` error when the client set the value of the '`save`' attribute to '`stream`'.
|
