You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@@ -82,12 +82,12 @@ All options can be changed in runtime by running \fIejabberdctl reload\-config\f
82
82
.sp
83
83
Some options can be specified for particular virtual host(s) only using \fIhost_config\fR or \fIappend_host_config\fR options\&. Such options are called \fIlocal\fR\&. Examples are \fImodules\fR, \fIauth_method\fR and \fIdefault_db\fR\&. The options that cannot be defined per virtual host are called \fIglobal\fR\&. Examples are \fIloglevel\fR, \fIcertfiles\fR and \fIlisten\fR\&. It is a configuration mistake to put \fIglobal\fR options under \fIhost_config\fR or \fIappend_host_config\fR section \- ejabberd will refuse to load such configuration\&.
84
84
.sp
85
-
It is not recommended to write ejabberd\&.yml from scratch\&. Instead it is better to start from "default" configuration file available at https://github\&.com/processone/ejabberd/blob/25\&.08/ejabberd\&.yml\&.example\&. Once you get ejabberd running you can start changing configuration options to meet your requirements\&.
85
+
It is not recommended to write ejabberd\&.yml from scratch\&. Instead it is better to start from "default" configuration file available at https://github\&.com/processone/ejabberd/blob/25\&.10/ejabberd\&.yml\&.example\&. Once you get ejabberd running you can start changing configuration options to meet your requirements\&.
86
86
.sp
87
87
Note that this document is intended to provide comprehensive description of all configuration options that can be consulted to understand the meaning of a particular option, its format and possible values\&. It will be quite hard to understand how to configure ejabberd by reading this document only \- for this purpose the reader is recommended to read online Configuration Guide available at https://docs\&.ejabberd\&.im/admin/configuration\&.
88
88
.SH "TOP LEVEL OPTIONS"
89
89
.sp
90
-
This section describes top level options of ejabberd 25\&.08\&. The options that changed in this version are marked with 🟤\&.
90
+
This section describes top level options of ejabberd 25\&.10\&. The options that changed in this version are marked with 🟤\&.
@@ -1282,17 +1282,12 @@ This option can be used to tune tick time parameter of
1282
1282
\fI1minute\fR\&.
1283
1283
.RE
1284
1284
.PP
1285
-
\fBnew_sql_schema\fR: \fItrue|false\fR
1285
+
\fBnew_sql_schema🟤\fR: \fItrue|false\fR
1286
1286
.RS4
1287
-
Whether to use the
1288
-
\fIdatabase\&.md#default\-and\-new\-schemas|newSQLschema\fR\&. All schemas are located at
1289
-
https://github\&.com/processone/ejabberd/tree/25\&.08/sql\&. There are two schemas available\&. The default legacy schema stores one XMPP domain into one ejabberd database\&. The
1290
-
\fInew\fR
1291
-
schema can handle several XMPP domains in a single ejabberd database\&. Using this
1292
-
\fInew\fR
1293
-
schema is best when serving several XMPP domains and/or changing domains from time to time\&. This avoid need to manage several databases and handle complex configuration changes\&. The default depends on configuration flag
1294
-
\fI\-\-enable\-new\-sql\-schema\fR
1295
-
which is set at compile time\&.
1287
+
\fINote\fR
1288
+
about this option: obsoleted in 25\&.10\&. This option was renamed to
1289
+
\fIsql_schema_multihost\fR
1290
+
in ejabberd 25\&.10\&. Please update your configuration to use the new option name
1296
1291
.RE
1297
1292
.PP
1298
1293
\fBoauth_access\fR: \fIAccessName\fR
@@ -1958,6 +1953,22 @@ or
1958
1953
if the latter is not set\&.
1959
1954
.RE
1960
1955
.PP
1956
+
\fBsql_schema_multihost🟤\fR: \fItrue|false\fR
1957
+
.RS4
1958
+
\fINote\fR
1959
+
about this option: renamed in 25\&.10\&. Whether to use the
1960
+
\fIdatabase\&.md#default\-and\-new\-schemas|multihostSQLschema\fR\&. All schemas are located at
1961
+
https://github\&.com/processone/ejabberd/tree/25\&.10/sql\&. There are two schemas available\&. The legacy
1962
+
\fIsinglehost\fR
1963
+
schema stores one XMPP domain into one ejabberd database\&. The
1964
+
\fImultihost\fR
1965
+
schema can handle several XMPP domains in a single ejabberd database\&. The
1966
+
\fImultihost\fR
1967
+
schema is preferable when serving several XMPP domains and/or changing domains from time to time\&. This avoid need to manage several databases and handle complex configuration changes\&. The default depends on configuration flag
This section describes modules options of ejabberd 25\&.08\&. The modules that changed in this version are marked with 🟤\&.
2121
+
This section describes modules options of ejabberd 25\&.10\&. The modules that changed in this version are marked with 🟤\&.
2111
2122
.SS "mod_adhoc"
2112
2123
.sp
2113
2124
def:ad\-hoc command
@@ -2277,7 +2288,7 @@ This module can be used to update existing SQL database from the default to the
2277
2288
The module has no options\&.
2278
2289
.SS "mod_announce"
2279
2290
.sp
2280
-
This module enables configured users to broadcast announcements and to set the message of the day (MOTD)\&. Configured users can perform these actions with an XMPP client either using Ad\-Hoc Commands or sending messages to specific JIDs\&.
2291
+
This module enables configured users to broadcast announcements and to set the message of the day (MOTD)\&. Configured users can perform these actions with an XMPP client either using Ad\-Hoc Commands or sending messages to specific JIDs\&. Equivalent API commands are also available\&.
@@ -2708,9 +2723,11 @@ The option is supposed to be used when
2708
2723
\fIallow_local_users\fR
2709
2724
and
2710
2725
\fIallow_transports\fR
2711
-
are not enough\&. It\(cqs an ACL where
2726
+
are not enough\&. It\(cqs an Access Rule where
2712
2727
\fIdeny\fR
2713
-
means the message will be rejected (or a CAPTCHA would be generated for a presence, if configured), and
2728
+
means the stanza will be rejected; there\(cqs an exception if option
2729
+
\fIcaptcha\fR
2730
+
is configured\&. And
2714
2731
\fIallow\fR
2715
2732
means the sender is whitelisted and the stanza will pass through\&. The default value is
2716
2733
\fInone\fR, which means nothing is whitelisted\&.
@@ -2732,7 +2749,7 @@ and some server\(cqs JID is in user\(cqs roster, then messages from any user of
2732
2749
.PP
2733
2750
\fBcaptcha\fR: \fItrue|false\fR
2734
2751
.RS4
2735
-
Whether to generate CAPTCHA or not in response to messages from strangers\&. See also section
2752
+
Whether to generate CAPTCHA challenges in response to incoming presence subscription requests from strangers\&. See also section
2736
2753
\fIbasic\&.md#captcha|CAPTCHA\fR
2737
2754
of the Configuration Guide\&. The default value is
2738
2755
\fIfalse\fR\&.
@@ -2956,7 +2973,9 @@ While a client is inactive, queue presence stanzas that indicate (un)availabilit
2956
2973
\fItrue\fR\&.
2957
2974
.RE
2958
2975
.RE
2959
-
.SS "mod_configure"
2976
+
.SS "mod_configure 🟤"
2977
+
.sp
2978
+
\fINote\fR about this option: improved in 25\&.10\&.
2960
2979
.sp
2961
2980
The module provides server configuration functionalities using XEP\-0030: Service Discovery and XEP\-0050: Ad\-Hoc Commands:
2962
2981
.sp
@@ -2994,6 +3013,100 @@ XEP\-0133: Service Administration
2994
3013
Additional custom ad\-hoc commands specific to ejabberd
2995
3014
.RE
2996
3015
.sp
3016
+
Ad\-hoc commands from XEP\-0133 that behave differently to the XEP:
3017
+
.sp
3018
+
.RS4
3019
+
.ien\{\
3020
+
\h'-04'\(bu\h'+03'\c
3021
+
.\}
3022
+
.el\{\
3023
+
.sp-1
3024
+
.IP\(bu2.3
3025
+
.\}
3026
+
get\-user\-roster: returns standard fields instead of roster items that client cannot display
3027
+
.RE
3028
+
.sp
3029
+
Those ad\-hoc commands from XEP\-0133 do not include in the response the client that executed the command:
3030
+
.sp
3031
+
.RS4
3032
+
.ien\{\
3033
+
\h'-04'\(bu\h'+03'\c
3034
+
.\}
3035
+
.el\{\
3036
+
.sp-1
3037
+
.IP\(bu2.3
3038
+
.\}
3039
+
get\-active\-users\-num
3040
+
.RE
3041
+
.sp
3042
+
.RS4
3043
+
.ien\{\
3044
+
\h'-04'\(bu\h'+03'\c
3045
+
.\}
3046
+
.el\{\
3047
+
.sp-1
3048
+
.IP\(bu2.3
3049
+
.\}
3050
+
get\-idle\-users\-num
3051
+
.RE
3052
+
.sp
3053
+
.RS4
3054
+
.ien\{\
3055
+
\h'-04'\(bu\h'+03'\c
3056
+
.\}
3057
+
.el\{\
3058
+
.sp-1
3059
+
.IP\(bu2.3
3060
+
.\}
3061
+
get\-active\-users
3062
+
.RE
3063
+
.sp
3064
+
.RS4
3065
+
.ien\{\
3066
+
\h'-04'\(bu\h'+03'\c
3067
+
.\}
3068
+
.el\{\
3069
+
.sp-1
3070
+
.IP\(bu2.3
3071
+
.\}
3072
+
get\-idle\-users
3073
+
.RE
3074
+
.sp
3075
+
Those ad\-hoc commands from XEP\-0133 are not implemented:
3076
+
.sp
3077
+
.RS4
3078
+
.ien\{\
3079
+
\h'-04'\(bu\h'+03'\c
3080
+
.\}
3081
+
.el\{\
3082
+
.sp-1
3083
+
.IP\(bu2.3
3084
+
.\}
3085
+
edit\-blacklist
3086
+
.RE
3087
+
.sp
3088
+
.RS4
3089
+
.ien\{\
3090
+
\h'-04'\(bu\h'+03'\c
3091
+
.\}
3092
+
.el\{\
3093
+
.sp-1
3094
+
.IP\(bu2.3
3095
+
.\}
3096
+
edit\-whitelist
3097
+
.RE
3098
+
.sp
3099
+
.RS4
3100
+
.ien\{\
3101
+
\h'-04'\(bu\h'+03'\c
3102
+
.\}
3103
+
.el\{\
3104
+
.sp-1
3105
+
.IP\(bu2.3
3106
+
.\}
3107
+
edit\-admin
3108
+
.RE
3109
+
.sp
2997
3110
This module requires \fImod_adhoc\fR (to execute the commands), and recommends \fImod_disco\fR (to discover the commands)\&.
2998
3111
.sp
2999
3112
Please notice that all the ad\-hoc commands implemented by this module have an equivalent API Command that you can execute using \fImod_adhoc_api\fR or any other API frontend\&.
@@ -4091,6 +4204,13 @@ This access rule defines who is allowed to modify the MAM preferences\&. The def
4091
4204
\fIall\fR\&.
4092
4205
.RE
4093
4206
.PP
4207
+
\fBarchive_muc_as_mucsub🟤\fR: \fItrue|false\fR
4208
+
.RS4
4209
+
\fINote\fR
4210
+
about this option: added in 25\&.10\&. When this option is enabled incoming groupchat messages for users that have mucsub subscription to a room from which message originated will have those messages archived after being converted to mucsub event messages\&.The default value is
4211
+
\fIfalse\fR\&.
4212
+
.RE
4213
+
.PP
4094
4214
\fBassume_mam_usage\fR: \fItrue|false\fR
4095
4215
.RS4
4096
4216
This option determines how ejabberd\(cqs stream management code (see
@@ -4176,7 +4296,7 @@ When this option is disabled, for each individual subscriber a separate mucsub m
0 commit comments