From 07501f8085e7813310c08a40360eb0b6b9b41c65 Mon Sep 17 00:00:00 2001 From: Evgeniy Khramtsov Date: Thu, 10 Jul 2014 19:07:09 +0400 Subject: [PATCH] Re-generate the HTML documents --- doc/dev.html | 448 +++++++++++++++++---------------- doc/features.html | 183 +++++++------- doc/guide.html | 614 +++++++++++++++++++++++++++------------------- 3 files changed, 696 insertions(+), 549 deletions(-) diff --git a/doc/dev.html b/doc/dev.html index bff534bfb..9c96d2716 100644 --- a/doc/dev.html +++ b/doc/dev.html @@ -1,40 +1,45 @@ - - - -Ejabberd 2.1.12 Developers Guide - - - - - - - + +Ejabberd community 14.05-120-gedfb5fc Developers Guide + + + -

+

-

-

Ejabberd 2.1.12 Developers Guide

Alexey Shchepin
- mailto:alexey@sevcom.net
- xmpp:aleksey@jabber.ru

+

+

Ejabberd community 14.05-120-gedfb5fc Developers Guide

Alexey Shchepin
+ mailto:alexey@sevcom.net
+ xmpp:aleksey@jabber.ru

-logo.png +logo.png -
I can thoroughly recommend ejabberd for ease of setup – -Kevin Smith, Current maintainer of the Psi project
-

Contents

Introduction -

ejabberd is a free and open source instant messaging server written in Erlang/OTP.

ejabberd is cross-platform, distributed, fault-tolerant, and based on open standards to achieve real-time communication.

ejabberd is designed to be a rock-solid and feature rich XMPP server.

ejabberd is suitable for small deployments, whether they need to be scalable or not, as well as extremely big deployments.

-

1  Key Features

- -

ejabberd is: -

I can thoroughly recommend ejabberd for ease of setup – +Kevin Smith, Current maintainer of the Psi project
+

Contents

Introduction +

ejabberd is a free and open source instant messaging server written in Erlang/OTP.

ejabberd is cross-platform, distributed, fault-tolerant, and based on open standards to achieve real-time communication.

ejabberd is designed to be a rock-solid and feature rich XMPP server.

ejabberd is suitable for small deployments, whether they need to be scalable or not, as well as extremely big deployments.

+ +

1  Key Features

+ +

ejabberd is: +

-

2  Additional Features

- -

Moreover, ejabberd comes with a wide range of other state-of-the-art features: -

+ +

2  Additional Features

+ +

Moreover, ejabberd comes with a wide range of other state-of-the-art features: +

+ + +

3  How it Works

+

A XMPP domain is served by one or more ejabberd nodes. These nodes can be run on different machines that are connected via a network. They all must have the ability to connect to port 4369 of all another nodes, and must have the same magic cookie (see Erlang/OTP documentation, in other words the file -~ejabberd/.erlang.cookie must be the same on all nodes). This is +~ejabberd/.erlang.cookie must be the same on all nodes). This is needed because all nodes exchange information about connected users, S2S -connections, registered services, etc…

Each ejabberd node have following modules: -

+ +

3.1  Router

This module is the main router of XMPP packets on each node. It routes them based on their destinations domains. It has two tables: local and global routes. First, domain of packet destination searched in local table, and if it found, then the packet is routed to appropriate process. If no, then it -searches in global table, and is routed to the appropriate ejabberd node or +searches in global table, and is routed to the appropriate ejabberd node or process. If it does not exists in either tables, then it sent to the S2S -manager.

-

3.2  Local Router

This module routes packets which have a destination domain equal to this server +manager.

+ +

3.2  Local Router

This module routes packets which have a destination domain equal to this server name. If destination JID has a non-empty user part, then it routed to the -session manager, else it is processed depending on it’s content.

-

3.3  Session Manager

This module routes packets to local users. It searches for what user resource +session manager, else it is processed depending on it’s content.

+ +

3.3  Session Manager

This module routes packets to local users. It searches for what user resource packet must be sent via presence table. If this resource is connected to this node, it is routed to C2S process, if it connected via another node, then -the packet is sent to session manager on that node.

-

3.4  S2S Manager

This module routes packets to other XMPP servers. First, it checks if an +the packet is sent to session manager on that node.

+ +

3.4  S2S Manager

This module routes packets to other XMPP servers. First, it checks if an open S2S connection from the domain of the packet source to the domain of packet destination already exists. If it is open on another node, then it routes the packet to S2S manager on that node, if it is open on this node, then it is routed to the process that serves this connection, and if a connection -does not exist, then it is opened and registered.

-

4  Authentication

-

4.0.1  External

- -

The external authentication script follows -the erlang port driver API.

That script is supposed to do theses actions, in an infinite loop: -

Example python script +

#!/usr/bin/python
 
 import sys
 from struct import *
@@ -242,10 +260,11 @@ while True:
     elif data[0] == "setpass":
         success = setpass(data[1], data[2], data[3])
     to_ejabberd(success)
-
-

5  XML Representation

-

Each XML stanza is represented as the following tuple: -

XMLElement = {xmlelement, Name, Attrs, [ElementOrCDATA]}
+
+ +

5  XML Representation

+

Each XML stanza is represented as the following tuple: +

XMLElement = {xmlelement, Name, Attrs, [ElementOrCDATA]}
         Name = string()
         Attrs = [Attr]
         Attr = {Key, Val}
@@ -253,30 +272,31 @@ while True:
         Val = string()
         ElementOrCDATA = XMLElement | CDATA
         CDATA = {xmlcdata, string()}
-

E. g. this stanza: -

<message to='test@conference.example.org' type='groupchat'>
+

E. g. this stanza: +

<message to='test@conference.example.org' type='groupchat'>
   <body>test</body>
 </message>
-

is represented as the following structure: -

{xmlelement, "message",
+

is represented as the following structure: +

{xmlelement, "message",
     [{"to", "test@conference.example.org"},
      {"type", "groupchat"}],
     [{xmlelement, "body",
          [],
          [{xmlcdata, "test"}]}]}}
-
-

6  Module xml

-

-
element_to_string(El) -> string() -
El = XMLElement
-
Returns string representation of XML stanza El.
crypt(S) -> string() -
S = string()
-
Returns string which correspond to S with encoded XML special -characters.
remove_cdata(ECList) -> EList -
ECList = [ElementOrCDATA]
+
+ +

6  Module xml

+

+
element_to_string(El) -> string() +
El = XMLElement
+
Returns string representation of XML stanza El.
crypt(S) -> string() +
S = string()
+
Returns string which correspond to S with encoded XML special +characters.
remove_cdata(ECList) -> EList +
ECList = [ElementOrCDATA]
 EList = [XMLElement]
-
EList is a list of all non-CDATA elements of ECList.
get_path_s(El, Path) -> Res -
El = XMLElement
+
EList is a list of all non-CDATA elements of ECList.
get_path_s(El, Path) -> Res +
El = XMLElement
 Path = [PathItem]
 PathItem = PathElem | PathAttr | PathCDATA
 PathElem = {elem, Name}
@@ -284,57 +304,60 @@ PathAttr = {attr, Name}
 PathCDATA = cdata
 Name = string()
 Res = string() | XMLElement
-
If Path is empty, then returns El. Else sequentially -consider elements of Path. Each element is one of: -
-
{elem, Name} Name is name of subelement of -El, if such element exists, then this element considered in +If Path is empty, then returns El. Else sequentially +consider elements of Path. Each element is one of: +
+
{elem, Name} Name is name of subelement of +El, if such element exists, then this element considered in following steps, else returns empty string. -
{attr, Name} If El have attribute Name, then +
{attr, Name} If El have attribute Name, then returns value of this attribute, else returns empty string. -
cdata Returns CDATA of El. -
TODO: -
         get_cdata/1, get_tag_cdata/1
+
cdata Returns CDATA of El. +
TODO: +
         get_cdata/1, get_tag_cdata/1
          get_attr/2, get_attr_s/2
          get_tag_attr/2, get_tag_attr_s/2
          get_subtag/2
-
-

7  Module xml_stream

-

-
parse_element(Str) -> XMLElement | {error, Err} -
Str = string()
+
+ +

7  Module xml_stream

+

+
parse_element(Str) -> XMLElement | {error, Err} +
Str = string()
 Err = term()
-
Parses Str using XML parser, returns either parsed element or error +Parses Str using XML parser, returns either parsed element or error tuple. -
-

8  Modules

-

-

8.1  Module gen_iq_handler

-

The module gen_iq_handler allows to easily write handlers for IQ packets -of particular XML namespaces that addressed to server or to users bare JIDs.

In this module the following functions are defined: -

-
add_iq_handler(Component, Host, NS, Module, Function, Type) -
Component = Module = Function = atom()
+
+ +

8  Modules

+

+ +

8.1  Module gen_iq_handler

+

The module gen_iq_handler allows to easily write handlers for IQ packets +of particular XML namespaces that addressed to server or to users bare JIDs.

In this module the following functions are defined: +

+
add_iq_handler(Component, Host, NS, Module, Function, Type) +
Component = Module = Function = atom()
 Host = NS = string()
 Type = no_queue | one_queue | parallel
-
Registers function Module:Function as handler for IQ packets on -virtual host Host that contain child of namespace NS in -Component. Queueing discipline is Type. There are at least +Registers function Module:Function as handler for IQ packets on +virtual host Host that contain child of namespace NS in +Component. Queueing discipline is Type. There are at least two components defined: -
-
ejabberd_local Handles packets that addressed to server JID; -
ejabberd_sm Handles packets that addressed to users bare JIDs. -
-
remove_iq_handler(Component, Host, NS) -
Component = atom()
+

+
ejabberd_local Handles packets that addressed to server JID;
+
ejabberd_sm Handles packets that addressed to users bare JIDs.
+

+
remove_iq_handler(Component, Host, NS) +
Component = atom()
 Host = NS = string()
-
Removes IQ handler on virtual host Host for namespace NS from -Component. -

Handler function must have the following type: -

-
Module:Function(From, To, IQ) -
From = To = jid()
-
-module(mod_cputime).
+
Removes IQ handler on virtual host Host for namespace NS from +Component. +

Handler function must have the following type: +

+
Module:Function(From, To, IQ) +
From = To = jid()
+
-module(mod_cputime).
 
 -behaviour(gen_mod).
 
@@ -368,9 +391,10 @@ process_local_iq(From, To, {iq, ID, Type, XMLNS, SubEl}) ->
                [{"xmlns", ?NS_CPUTIME}],
                [{xmlelement, "cputime", [], [{xmlcdata, SCPUTime}]}]}]}
     end.
-
-

8.2  Services

-

-module(mod_echo).
+
+ +

8.2  Services

+

-module(mod_echo).
 
 -behaviour(gen_mod).
 
@@ -404,10 +428,10 @@ stop(Host) ->
     Proc = gen_mod:get_module_proc(Host, ?PROCNAME),
     Proc ! stop,
     {wait, Proc}.
-
+ -
This document was translated from LATEX by -HEVEA.
- +
This document was translated from LATEX by +HEVEA.
+ diff --git a/doc/features.html b/doc/features.html index bd7cb666f..f922a1cca 100644 --- a/doc/features.html +++ b/doc/features.html @@ -1,40 +1,45 @@ - - - -Ejabberd 2.1.12 Feature Sheet - - - - - - - + +Ejabberd community 14.05-120-gedfb5fc Feature Sheet + + + -

+

-

-

Ejabberd 2.1.12 Feature Sheet

Sander Devrieze
- mailto:s.devrieze@pandora.be
- xmpp:sander@devrieze.dyndns.org

+

+

Ejabberd community 14.05-120-gedfb5fc Feature Sheet

Sander Devrieze
+ mailto:s.devrieze@pandora.be
+ xmpp:sander@devrieze.dyndns.org

-logo.png +logo.png -
I can thoroughly recommend ejabberd for ease of setup – -Kevin Smith, Current maintainer of the Psi project

Introduction -

I just tried out ejabberd and was impressed both by ejabberd itself and the language it is written in, Erlang. — -Joeri

ejabberd is a free and open source instant messaging server written in Erlang/OTP.

ejabberd is cross-platform, distributed, fault-tolerant, and based on open standards to achieve real-time communication.

ejabberd is designed to be a rock-solid and feature rich XMPP server.

ejabberd is suitable for small deployments, whether they need to be scalable or not, as well as extremely big deployments.

-

Key Features

- -

Erlang seems to be tailor-made for writing stable, robust servers. — -Peter Saint-André, Executive Director of the Jabber Software Foundation

ejabberd is: -

I can thoroughly recommend ejabberd for ease of setup – +Kevin Smith, Current maintainer of the Psi project

Introduction +

I just tried out ejabberd and was impressed both by ejabberd itself and the language it is written in, Erlang. — +Joeri

ejabberd is a free and open source instant messaging server written in Erlang/OTP.

ejabberd is cross-platform, distributed, fault-tolerant, and based on open standards to achieve real-time communication.

ejabberd is designed to be a rock-solid and feature rich XMPP server.

ejabberd is suitable for small deployments, whether they need to be scalable or not, as well as extremely big deployments.

+ +

Key Features

+ +

Erlang seems to be tailor-made for writing stable, robust servers. — +Peter Saint-André, Executive Director of the Jabber Software Foundation

ejabberd is: +

-

Additional Features

- -

ejabberd is making inroads to solving the "buggy incomplete server" problem — -Justin Karneges, Founder of the Psi and the Delta projects

Moreover, ejabberd comes with a wide range of other state-of-the-art features: -

+ +

Additional Features

+ +

ejabberd is making inroads to solving the "buggy incomplete server" problem — +Justin Karneges, Founder of the Psi and the Delta projects

Moreover, ejabberd comes with a wide range of other state-of-the-art features: +

+ -
This document was translated from LATEX by -HEVEA.
- +
This document was translated from LATEX by +HEVEA.
+ diff --git a/doc/guide.html b/doc/guide.html index c583a8331..e1aefd053 100644 --- a/doc/guide.html +++ b/doc/guide.html @@ -64,7 +64,7 @@ BLOCKQUOTE.figure DIV.center DIV.center HR{display:none;} - ejabberd community + ejabberd community 14.05-120-gedfb5fc Installation and Operation Guide @@ -84,7 +84,7 @@ BLOCKQUOTE.figure DIV.center DIV.center HR{display:none;}


- +
ejabberd community
@@ -143,93 +143,94 @@ BLOCKQUOTE.figure DIV.center DIV.center HR{display:none;} -
  • 3.3  Modules Configuration +
  • 3.3  Modules Configuration
    • -
  • Chapter 4  Managing an ejabberd Server +
  • Chapter 4  Managing an ejabberd Server -
  • Chapter 5  Securing ejabberd +
  • Chapter 5  Securing ejabberd -
  • Chapter 6  Clustering +
  • Chapter 6  Clustering -
  • Chapter 7  Debugging +
  • Chapter 7  Debugging -
  • Appendix A  Internationalization and Localization -
  • Appendix B  Release Notes -
  • Appendix C  Acknowledgements -
  • Appendix D  Copyright Information +
  • Appendix A  Internationalization and Localization +
  • Appendix B  Release Notes +
  • Appendix C  Acknowledgements +
  • Appendix D  Copyright Information

    • Chapter 1  Introduction

    @@ -277,11 +278,12 @@ Internal database for fast deployment (Mnesia).

  • Native MySQL support.
  • Native PostgreSQL support.
  • ODBC data storage support. -
  • Microsoft SQL Server support.
    • +
  • Microsoft SQL Server support.
  • Riak NoSQL database support. +
  • Authentication
  • Others

    2.4.2  Download Source Code

    @@ -416,8 +417,7 @@ To get the full list run the command: Enable the use of development tools.

    --enable-mysql
    Enable MySQL support (see section 3.2.1).
    --enable-pgsql
    Enable PostgreSQL support (see section 3.2.1).
    --enable-zlib
    -Enable Stream Compression (XEP-0138) using zlib.
    --enable-stun
    -Enable STUN/TURN support (see section 3.1.10).
    --enable-iconv
    +Enable Stream Compression (XEP-0138) using zlib.
    --enable-iconv
    Enable iconv support. This is needed for mod_irc (see seciont 3.3.8).
    --enable-debug
    Compile with +debug_info enabled.

    --enable-full-xml
    Enable the use of XML based optimisations. @@ -798,7 +798,7 @@ Handles XML-RPC requests to execute ejabberd commands (4 Options: access_commands, maxsessions, timeout.
    You can find option explanations, example configuration in old and new format, and example calls in several languages in the old -    ejabberd_xmlrpc README.txt +ejabberd_xmlrpc documentation.

    Options

    This is a detailed description of each option allowed by the listening modules: @@ -818,8 +818,10 @@ To define a certificate file specific for a given domain, use the global option

    ciphers: Ciphers
    OpenSSL ciphers list in the same format accepted by ‘openssl ciphers’ command.
    protocol_options: ProtocolOpts
    -List of general options relating to SSL/TLS. These map to <a href="https://www.openssl.org/docs/ssl/SSL_CTX_set_options.html">OpenSSL's set_options()</a>. -For a full list of options available in ejabberd, <a href="https://github.com/processone/tls/blob/master/c_src/options.h">see the source</a>. +List of general options relating to SSL/TLS. These map to +OpenSSL’s set_options(). +For a full list of options available in ejabberd, +see the source. The default entry is: "no_sslv2"
    default_host: undefined|HostName}
    If the HTTP request received by ejabberd contains the HTTP header Host @@ -861,10 +863,10 @@ in seconds: {http_poll_timeout, 300}.

    max_ack_queue: Size
    This option specifies the maximum number of unacknowledged stanzas queued for possible retransmission if stream_management is -enabled. When the limit is reached, the first stanza is dropped from -the queue before adding the next one. This option can be specified -for ejabberd_c2s listeners. The allowed values are positive -integers and infinity. Default value: 500. +enabled. When the limit is exceeded, the client session is +terminated. This option can be specified for ejabberd_c2s +listeners. The allowed values are positive integers and +infinity. Default value: 500.
    max_fsm_queue: Size
    This option specifies the maximum number of elements in the queue of the FSM (Finite State Machine). @@ -986,8 +988,10 @@ Full path to the file containing the SSL certificate for a specific domain.
    s2s_ciphers: Ciphers
    OpenSSL ciphers list in the same format accepted by ‘openssl ciphers’ command.
    s2s_protocol_options: ProtocolOpts
    -List of general options relating to SSL/TLS. These map to <a href="https://www.openssl.org/docs/ssl/SSL_CTX_set_options.html">OpenSSL's set_options()</a>. -For a full list of options available in ejabberd, <a href="https://github.com/processone/tls/blob/protocol_options/c_src/options.h">see the source</a>. +List of general options relating to SSL/TLS. These map to +OpenSSL’s set_options(). +For a full list of options available in ejabberd, +see the source. The default entry is: "no_sslv2"
    outgoing_s2s_families: [Family, ...]
    Specify which address families to try, in what order. @@ -1911,7 +1915,7 @@ listen:

    3.2  Database and LDAP Configuration

    ejabberd uses its internal Mnesia database by default. However, it is -possible to use a relational database or an LDAP server to store persistent, +possible to use a relational database, key-value storage or an LDAP server to store persistent, long-living data. ejabberd is very flexible: you can configure different authentication methods for different virtual hosts, you can configure different authentication mechanisms for the same virtual host (fallback), you can set @@ -1921,6 +1925,7 @@ different storage systems for modules, and so forth.

    The following databas

  • MySQL
  • Any ODBC compatible database
  • PostgreSQL +
  • Riak

    • The following LDAP servers are tested with ejabberd:

    - -

    3.3.1  Modules Overview

    + +

    3.3.1  Modules Overview

    The following table lists all modules included in ejabberd.

    ejabberd community 14.05-120-gedfb5fc
     
    Installation and Operation Guide
    @@ -2279,18 +2337,18 @@ options are specified between the square brackets:

    You can see which database backend each module needs by looking at the suffix:

    You can find more contributed modules on the ejabberd website. Please remember that these contributions might not work or that they can contain severe bugs and security leaks. Therefore, use them at your own risk!

    - -

    3.3.2  Common Options

    The following options are used by many modules. Therefore, they are described in + +

    3.3.2  Common Options

    The following options are used by many modules. Therefore, they are described in this separate section.

    - -

    iqdisc

    + +

    iqdisc

    Many modules define handlers for processing IQ queries of different namespaces to this server or to a user (e. g. to example.org or to user@example.org). This option defines processing discipline for @@ -2321,8 +2379,8 @@ number of processes (32000 by default). iqdisc: no_queue ...

    - -

    host

    + +

    host

    This option defines the Jabber ID of a service provided by an ejabberd module.

    The syntax is:

    host: HostName

    If you include the keyword "@HOST@" in the HostName, it is replaced at start time with the real virtual host string.

    This example configures @@ -2341,8 +2399,8 @@ the "@HOST@" keyword must be used: host: "mirror.@HOST@" ...

    - -

    3.3.3  mod_announce

    + +

    3.3.3  mod_announce

    This module enables configured users to broadcast announcements and to set the message of the day (MOTD). Configured users can perform these actions with a @@ -2416,8 +2474,8 @@ modules:

    Note that mod_announce can be resource intensive on large deployments as it can broadcast lot of messages. This module should be disabled for instances of ejabberd with hundreds of thousands users.

    - -

    3.3.4  mod_disco

    + +

    3.3.4  mod_disco

    @@ -2499,8 +2557,8 @@ and admin addresses for both the main server and the vJUD service: - "xmpp:admins@shakespeare.lit" ...

    - -

    3.3.5  mod_echo

    + +

    3.3.5  mod_echo

    This module simply echoes any XMPP packet back to the sender. This mirror can be of interest for ejabberd and XMPP client debugging.

    Options: @@ -2519,8 +2577,8 @@ of them all? host: "mirror.example.org" ...

    - -

    3.3.6  mod_http_bind

    + +

    3.3.6  mod_http_bind

    This module implements XMPP over Bosh (formerly known as HTTP Binding) as defined in XEP-0124 and XEP-0206. It extends ejabberd’s built in HTTP service with a configurable @@ -2567,8 +2625,8 @@ For example, to set 50 seconds: max_inactivity: 50 ...

    - -

    3.3.7  mod_http_fileserver

    + +

    3.3.7  mod_http_fileserver

    This simple module serves files from the local disk over HTTP.

    Options:

    docroot: Path
    @@ -2627,8 +2685,8 @@ To use this module you must enable it: ... ...

    - -

    3.3.8  mod_irc

    + +

    3.3.8  mod_irc

    This module is an IRC transport that can be used to join channels on IRC servers.

    End user information: @@ -2698,8 +2756,8 @@ modules: host: "irc.example.net" ...

    - -

    3.3.9  mod_last

    + +

    3.3.9  mod_last

    This module adds support for Last Activity (XEP-0012). It can be used to discover when a disconnected user last accessed the server, to know when a connected user was last active on the server, or to query the uptime of the @@ -2712,8 +2770,8 @@ Define the type of storage where the module will create the tables and store use The default is to store in the internal Mnesia database. If odbc value is defined, make sure you have defined the database, see 3.2.

    - -

    3.3.10  mod_muc

    + +

    3.3.10  mod_muc

    This module provides a Multi-User Chat (XEP-0045) service. Users can discover existing rooms, join or create them. Occupants of a room can chat in public or have private chats.

    Some of the features of Multi-User Chat: @@ -2952,8 +3010,8 @@ the newly created rooms have by default those options. access_admin: muc_admin ...

    - -

    3.3.11  mod_muc_log

    + +

    3.3.11  mod_muc_log

    This module enables optional logging of Multi-User Chat (MUC) public conversations to HTML. Once you enable this module, users can join a room using a MUC capable XMPP client, and if they have enough privileges, they can request the @@ -3080,8 +3138,8 @@ modules: timezone: local ...

    - -

    3.3.12  mod_offline

    + +

    3.3.12  mod_offline

    This module implements offline message storage (XEP-0160). This means that all messages sent to an offline user will be stored on the server until that user comes @@ -3125,8 +3183,8 @@ modules: access_max_user_messages: max_user_offline_messages ...

    - -

    3.3.13  mod_ping

    + +

    3.3.13  mod_ping

    This module implements support for XMPP Ping (XEP-0199) and periodic keepalives. When this module is enabled ejabberd responds correctly to ping requests, as defined in the protocol.

    Configuration options: @@ -3155,8 +3213,8 @@ and if a client does not answer to the ping in less than 32 seconds, its connect timeout_action: kill ...

    - -

    3.3.14  mod_pres_counter

    + +

    3.3.14  mod_pres_counter

    This module detects flood/spam in presence subscription stanza traffic. If a user sends or receives more of those stanzas in a time interval, the exceeding stanzas are silently dropped, and warning is logged.

    Configuration options: @@ -3181,8 +3239,8 @@ to be sent or received by the users in 60 seconds: interval: 60 ...

    - -

    3.3.15  mod_privacy

    + +

    3.3.15  mod_privacy

    This module implements Blocking Communication (also known as Privacy Rules) as defined in section 10 from XMPP IM. If end users have support for it in their XMPP client, they will be able to: @@ -3214,8 +3272,8 @@ Define the type of storage where the module will create the tables and store use The default is to store in the internal Mnesia database. If odbc value is defined, make sure you have defined the database, see 3.2.

    - -

    3.3.16  mod_private

    + +

    3.3.16  mod_private

    This module adds support for Private XML Storage (XEP-0049):

    Using this method, XMPP entities can store private data on the server and @@ -3231,8 +3289,8 @@ Define the type of storage where the module will create the tables and store use The default is to store in the internal Mnesia database. If odbc value is defined, make sure you have defined the database, see 3.2.

    - -

    3.3.17  mod_proxy65

    + +

    3.3.17  mod_proxy65

    This module implements SOCKS5 Bytestreams (XEP-0065). It allows ejabberd to act as a file transfer proxy between two XMPP clients.

    Options: @@ -3305,8 +3363,8 @@ modules: shaper: proxy65_shaper ...

    - -

    3.3.18  mod_pubsub

    + +

    3.3.18  mod_pubsub

    This module offers a Publish-Subscribe Service (XEP-0060). The functionality in mod_pubsub can be extended using plugins. The plugin that implements PEP (Personal Eventing via Pubsub) (XEP-0163) @@ -3389,8 +3447,8 @@ The following example shows previous configuration with ODBC usage: - "pep" ...

    - -

    3.3.19  mod_register

    + +

    3.3.19  mod_register

    This module adds support for In-Band Registration (XEP-0077). This protocol enables end users to use a XMPP client to:

    - -

    3.3.20  mod_register_web

    + +

    3.3.20  mod_register_web

    This module provides a web page where people can:

    - -

    3.3.23  mod_shared_roster

    + +

    3.3.23  mod_shared_roster

    This module enables you to create shared roster groups. This means that you can create groups of people that can see members from (other) groups in their rosters. The big advantages of this feature are that end users do not need to @@ -3729,18 +3787,18 @@ roster groups as shown in the following table:

    ModuleFeatureDependencies
    mod_adhocAd-Hoc Commands (XEP-0050) 

    - -

    3.3.24  mod_shared_roster_ldap

    + +

    3.3.24  mod_shared_roster_ldap

    This module lets the server administrator automatically populate users’ rosters (contact lists) with entries based on users and groups defined in an LDAP-based directory.

    - -

    Configuration parameters

    The module accepts the following configuration parameters. Some of them, if + +

    Configuration parameters

    The module accepts the following configuration parameters. Some of them, if unspecified, default to the values specified for the top level of configuration. This lets you avoid specifying, for example, the bind password, in multiple places.

    - -
    Filters

    These parameters specify LDAP filters used to query for shared roster information. + +

    Filters

    These parameters specify LDAP filters used to query for shared roster information. All of them are run against the ldap_base.

    ldap_rfilter
    So called “Roster Filter”. Used to find names of all “shared roster” groups. See also the ldap_groupattr parameter. @@ -3778,8 +3836,8 @@ A symptom of this problem is that you will see messages such as the following in 

    get_filter: unknown filter type=130
 filter="(&(?=undefined)(?=undefined)(something=else))"

    - -

    Attributes

    These parameters specify the names of the attributes which hold interesting data + +

    Attributes

    These parameters specify the names of the attributes which hold interesting data in the entries returned by running filters specified in section 3.3.24.

    ldap_groupattr
    @@ -3808,8 +3866,8 @@ attribute in the roster item objects needs to match the ID retrieved from the Retrieved from results of the “User Filter”. Defaults to cn.

    - -

    Control parameters

    These paramters control the behaviour of the module.

    ldap_memberattr_format
    + +

    Control parameters

    These paramters control the behaviour of the module.

    ldap_memberattr_format
    A globbing format for extracting user ID from the value of the attribute named by ldap_memberattr. Defaults to %u, which means that the whole value is the member ID. If @@ -3844,12 +3902,12 @@ Number of seconds for which the cache for group membership is considered fresh after retrieval. 300 by default. See section 3.3.24 on how it is used during roster retrieval.

    - -

    Connection parameters

    The module also accepts the connection parameters, all of which default to the + +

    Connection parameters

    The module also accepts the connection parameters, all of which default to the top-level parameter of the same name, if unspecified. See 3.2.2 for more information about them.

    - -

    Retrieving the roster

    When the module is called to retrieve the shared roster for a user, the + +

    Retrieving the roster

    When the module is called to retrieve the shared roster for a user, the following algorithm is used:

    1. A list of names of groups to display is created: the Roster Filter is run against the base DN, retrieving the values of the attribute named by @@ -3883,13 +3941,13 @@ attributes named by ldap_useruid and user name cache.

    - -

    Configuration examples

    Since there are many possible + +

    Configuration examples

    Since there are many possible DIT layouts, it will probably be easiest to understand how to configure the module by looking at an example for a given DIT (or one resembling it).

    - -
    Flat DIT

    This seems to be the kind of DIT for which this module was initially designed. + +

    Flat DIT

    This seems to be the kind of DIT for which this module was initially designed. Basically there are just user objects, and group membership is stored in an attribute individually for each user. For example in a layout shown in figure 3.1, the group of each user is stored in its ou attribute.

    @@ -3926,8 +3984,8 @@ You can use the following configuration…

    modules

    - -
    Deep DIT

    This type of DIT contains distinctly typed objects for users and groups – see figure 3.3. + +

    Deep DIT

    This type of DIT contains distinctly typed objects for users and groups – see figure 3.3. They are shown separated into different subtrees, but it’s not a requirement.

    msrl-dit-deep.png @@ -3960,16 +4018,16 @@ the roster shown in figure 3.4.

    - -

    3.3.25  mod_sic

    + +

    3.3.25  mod_sic

    This module adds support for Server IP Check (XEP-0279). This protocol enables a client to discover its external IP address.

    Options:

    iqdisc: Discipline
    This specifies the processing discipline for urn:xmpp:sic:0 IQ queries (see section 3.3.2).

    - -

    3.3.26  mod_sip

    + +

    3.3.26  mod_sip

    This module adds SIP proxy/registrar support for the corresponding virtual host. Note that it is not enough to just load this module only. You should also configure @@ -3980,15 +4038,39 @@ listeners and DNS records properly. See section 3.1.11 for th ...

    Options:

    -via: [{type: Type, host: Host, port: Port}]
    With +record_route: SIP_URI
    When the option +always_record_route is set or when SIP outbound +is utilized RFC 5626, +ejabberd inserts Record-Route header field with this SIP_URI +into a SIP message. The default is SIP URI constructed from the virtual host. +
    always_record_route: true|false
    +Always insert Record-Route header into SIP messages. This approach allows +to bypass NATs/firewalls a bit more easily. The default is true. +
    routes: [SIP_URI]
    You can set a list of SIP URIs of routes +pointing to this proxy server. The default is a list of a SIP URI constructed +from the virtual host. +
    flow_timeout_udp: Seconds
    For SIP outbound UDP connections set a keep-alive +timer to Seconds. The default is 29. +
    flow_timeout_tcp: Seconds
    For SIP outbound TCP connections set a keep-alive +timer to Seconds. The default is 120. +
    via: [{type: Type, host: Host, port: Port}]
    With this option for every Type you can specify Host and Port to set in Via header of outgoing SIP messages, where Type can be udp, tcp or tls. Host is a string and Port is a non negative integer. This is useful if you’re running your server in a non-standard -network topology. Example configuration: -
    modules:
+network topology.
+

    +Example complex configuration: +

    modules:
   ...
   mod_sip:
+    always_record_route: false
+    record_route: sip:example.com;lr
+    routes:
+      - sip:example.com;lr
+      - sip:sip.example.com;lr
+    flow_timeout_udp: 30
+    flow_timeout_tcp: 130
     via:
       - 
         type: tls
@@ -4003,9 +4085,9 @@ network topology. Example configuration:
         host: "sip-udp.example.com"
         port: 5060
   ...
-

    - -

    3.3.27  mod_stats

    +

    + +

    3.3.27  mod_stats

    This module adds support for Statistics Gathering (XEP-0039). This protocol allows you to retrieve next statistics from your ejabberd deployment:

    • @@ -4037,16 +4119,16 @@ by sending: </query> </iq>

    - -

    3.3.28  mod_time

    + +

    3.3.28  mod_time

    This module features support for Entity Time (XEP-0202). By using this XEP, you are able to discover the time at another entity’s location.

    Options:

    iqdisc: Discipline
    This specifies the processing discipline for Entity Time (jabber:iq:time) IQ queries (see section 3.3.2).

    - -

    3.3.29  mod_vcard

    + +

    3.3.29  mod_vcard

    This module allows end users to store and retrieve their vCard, and to retrieve other users vCards, as defined in vcard-temp (XEP-0054). The module also implements an uncomplicated Jabber User Directory based on the vCards of @@ -4103,8 +4185,8 @@ and that all virtual hosts will be searched instead of only the current one: allow_return_all: true ...

    - -

    3.3.30  mod_vcard_ldap

    + +

    3.3.30  mod_vcard_ldap

    ejabberd can map LDAP attributes to vCard fields. This behaviour is implemented in the mod_vcard_ldap module. This module does not depend on the authentication method (see 3.2.2).

    Usually ejabberd treats LDAP as a read-only storage: @@ -4287,8 +4369,8 @@ searching his info in LDAP.

    • - -

    3.3.31  mod_vcard_xupdate

    + +

    3.3.31  mod_vcard_xupdate

    The user’s client can store an avatar in the user vCard. The vCard-Based Avatars protocol (XEP-0153) provides a method for clients to inform the contacts what is the avatar hash value. @@ -4308,8 +4390,8 @@ Define the type of storage where the module will create the tables and store use The default is to store in the internal Mnesia database. If odbc value is defined, make sure you have defined the database, see 3.2.

    - -

    3.3.32  mod_version

    + +

    3.3.32  mod_version

    This module implements Software Version (XEP-0092). Consequently, it answers ejabberd’s version when queried.

    Options:

    @@ -4318,10 +4400,10 @@ The default value is true.
    iqdisc: Discipline
    This specifies the processing discipline for Software Version (jabber:iq:version) IQ queries (see section 3.3.2).

    - -

    Chapter 4  Managing an ejabberd Server

    - -

    4.1  ejabberdctl

    With the ejabberdctl command line administration script + +

    Chapter 4  Managing an ejabberd Server

    + +

    4.1  ejabberdctl

    With the ejabberdctl command line administration script you can execute ejabberdctl commands (described in the next section, 4.1.1) and also many general ejabberd commands (described in section 4.2). This means you can start, stop and perform many other administrative tasks @@ -4334,8 +4416,8 @@ This can be used by other scripts to determine automatically if a command succeeded or failed, for example using: echo $?

    If you use Bash, you can get Bash completion by copying the file tools/ejabberdctl.bc to the directory /etc/bash_completion.d/ (in Debian, Ubuntu, Fedora and maybe others).

    - -

    4.1.1  ejabberdctl Commands

    When ejabberdctl is executed without any parameter, + +

    4.1.1  ejabberdctl Commands

    When ejabberdctl is executed without any parameter, it displays the available options. If there isn’t an ejabberd server running, the available parameters are:

    @@ -4371,8 +4453,8 @@ robot1 testuser1 testuser2

    - -

    4.1.2  Erlang Runtime System

    ejabberd is an Erlang/OTP application that runs inside an Erlang runtime system. + +

    4.1.2  Erlang Runtime System

    ejabberd is an Erlang/OTP application that runs inside an Erlang runtime system. This system is configured using environment variables and command line parameters. The ejabberdctl administration script uses many of those possibilities. You can configure some of them with the file ejabberdctl.cfg, @@ -4454,8 +4536,8 @@ not “Simple Authentication and Security Layer”.

    Note that some characters need to be escaped when used in shell scripts, for instance " and {}. You can find other options in the Erlang manual page (erl -man erl).

    - -

    4.2  ejabberd Commands

    An ejabberd command is an abstract function identified by a name, + +

    4.2  ejabberd Commands

    An ejabberd command is an abstract function identified by a name, with a defined number and type of calling arguments and type of result that is registered in the ejabberd_commands service. Those commands can be defined in any Erlang module and executed using any valid frontend.

    ejabberd includes two frontends to execute ejabberd commands: the script ejabberdctl (4.1) @@ -4463,8 +4545,8 @@ and the ejabberd_xmlrpc listener (mod_rest (HTTP POST service), mod_shcommands (ejabberd WebAdmin page).

    - -

    4.2.1  List of ejabberd Commands

    ejabberd includes a few ejabberd Commands by default. + +

    4.2.1  List of ejabberd Commands

    ejabberd includes a few ejabberd Commands by default. When more modules are installed, new commands may be available in the frontends.

    The easiest way to get a list of the available commands, and get help for them is to use the ejabberdctl script: 

    $ ejabberdctl help
@@ -4520,8 +4602,8 @@ is very high.
 
    register user host password
     Register an account in that domain with the given password.
 
    unregister user host
     Unregister the given account.
 
      
    
-
-
    4.2.2  Restrict Execution with AccessCommands
      
    The frontends can be configured to restrict access to certain commands.
+
+
    4.2.2  Restrict Execution with AccessCommands
      
    The frontends can be configured to restrict access to certain commands.
 In that case, authentication information must be provided.
 In each frontend the AccessCommands option is defined
 in a different place. But in all cases the option syntax is the same:
@@ -4565,8 +4647,8 @@ and the provided arguments do not contradict Arguments.
    As an example to u
  {_bot_reg_test, [register, unregister], [{host, "test.org"}]}
 ]

    - -

    4.3  Web Admin

    + +

    4.3  Web Admin

    The ejabberd Web Admin allows to administer most of ejabberd using a web browser.

    This feature is enabled by default: a ejabberd_http listener with the option web_admin (see section 3.1.4) is included in the listening ports. Then you can open @@ -4661,15 +4743,15 @@ The file is searched by default in The directory of the documentation can be specified in the environment variable EJABBERD_DOC_PATH. See section 4.1.2.

    - -

    4.4  Ad-hoc Commands

    If you enable mod_configure and mod_adhoc, + +

    4.4  Ad-hoc Commands

    If you enable mod_configure and mod_adhoc, you can perform several administrative tasks in ejabberd with an XMPP client. The client must support Ad-Hoc Commands (XEP-0050), and you must login in the XMPP server with an account with proper privileges.

    - -

    4.5  Change Computer Hostname

    ejabberd uses the distributed Mnesia database. + +

    4.5  Change Computer Hostname

    ejabberd uses the distributed Mnesia database. Being distributed, Mnesia enforces consistency of its file, so it stores the name of the Erlang node in it (see section 5.4). The name of an Erlang node includes the hostname of the computer. @@ -4715,10 +4797,10 @@ mv /var/lib/ejabberd/*.* /var/lib/ejabberd/oldfiles/

  • Check that the information of the old database is available: accounts, rosters... After you finish, remember to delete the temporary backup files from public directories.

    • - -

    Chapter 5  Securing ejabberd

    - -

    5.1  Firewall Settings

    + +

    Chapter 5  Securing ejabberd

    + +

    5.1  Firewall Settings

    You need to take the following TCP ports in mind when configuring your firewall:

    @@ -4729,8 +4811,8 @@ After you finish, remember to delete the temporary backup files from public dire
    PortDescription
    port rangeUsed for connections between Erlang nodes. This range is configurable (see section 5.2).

    - -

    5.2  epmd

    epmd (Erlang Port Mapper Daemon) + +

    5.2  epmd

    epmd (Erlang Port Mapper Daemon) is a small name server included in Erlang/OTP and used by Erlang programs when establishing distributed Erlang communications. ejabberd needs epmd to use ejabberdctl and also when clustering ejabberd nodes. @@ -4760,8 +4842,8 @@ the network interface where the Erlang node will listen and accept connections. The Erlang command-line parameter used internally is, for example: 

    erl ... -kernel inet_dist_use_interface "{127,0,0,1}"

    - -

    5.3  Erlang Cookie

    The Erlang cookie is a string with numbers and letters. + +

    5.3  Erlang Cookie

    The Erlang cookie is a string with numbers and letters. An Erlang node reads the cookie at startup from the command-line parameter -setcookie. If not indicated, the cookie is read from the cookie file $HOME/.erlang.cookie. If this file does not exist, it is created immediately with a random cookie. @@ -4775,8 +4857,8 @@ to prevent unauthorized access or intrusion to an Erlang node. The communication between Erlang nodes are not encrypted, so the cookie could be read sniffing the traffic on the network. The recommended way to secure the Erlang node is to block the port 4369.

    - -

    5.4  Erlang Node Name

    An Erlang node may have a node name. + +

    5.4  Erlang Node Name

    An Erlang node may have a node name. The name can be short (if indicated with the command-line parameter -sname) or long (if indicated with the parameter -name). Starting an Erlang node with -sname limits the communication between Erlang nodes to the LAN.

    Using the option -sname instead of -name is a simple method @@ -4785,8 +4867,8 @@ However, it is not ultimately effective to prevent access to the Erlang node, because it may be possible to fake the fact that you are on another network using a modified version of Erlang epmd. The recommended way to secure the Erlang node is to block the port 4369.

    - -

    5.5  Securing Sensitive Files

    ejabberd stores sensitive data in the file system either in plain text or binary files. + +

    5.5  Securing Sensitive Files

    ejabberd stores sensitive data in the file system either in plain text or binary files. The file system permissions should be set to only allow the proper user to read, write and execute those files and directories.

    ejabberd configuration file: /etc/ejabberd/ejabberd.yml
    @@ -4806,11 +4888,11 @@ so it is preferable to secure the whole /var
    Erlang cookie file: /var/lib/ejabberd/.erlang.cookie
    See section 5.3.

    - -

    Chapter 6  Clustering

    + +

    Chapter 6  Clustering

    - -

    6.1  How it Works

    + +

    6.1  How it Works

    A XMPP domain is served by one or more ejabberd nodes. These nodes can be run on different machines that are connected via a network. They all must have the ability to connect to port 4369 of all another nodes, and must @@ -4824,34 +4906,34 @@ router,

  • session manager,
  • s2s manager.

    • - -

    6.1.1  Router

    + +

    6.1.1  Router

    This module is the main router of XMPP packets on each node. It routes them based on their destination’s domains. It uses a global routing table. The domain of the packet’s destination is searched in the routing table, and if it is found, the packet is routed to the appropriate process. If not, it is sent to the s2s manager.

    - -

    6.1.2  Local Router

    + +

    6.1.2  Local Router

    This module routes packets which have a destination domain equal to one of this server’s host names. If the destination JID has a non-empty user part, it is routed to the session manager, otherwise it is processed depending on its content.

    - -

    6.1.3  Session Manager

    + +

    6.1.3  Session Manager

    This module routes packets to local users. It looks up to which user resource a packet must be sent via a presence table. Then the packet is either routed to the appropriate c2s process, or stored in offline storage, or bounced back.

    - -

    6.1.4  s2s Manager

    + +

    6.1.4  s2s Manager

    This module routes packets to other XMPP servers. First, it checks if an opened s2s connection from the domain of the packet’s source to the domain of the packet’s destination exists. If that is the case, the s2s manager routes the packet to the process serving this connection, otherwise a new connection is opened.

    - -

    6.2  Clustering Setup

    + +

    6.2  Clustering Setup

    Suppose you already configured ejabberd on one machine named (first), and you need to setup another one to make an ejabberd cluster. Then do following steps:

    1. @@ -4889,11 +4971,11 @@ and ‘access’ options because they will be taken from enabled only on one machine in the cluster.

    You can repeat these steps for other machines supposed to serve this domain.

    - -

    6.3  Service Load-Balancing

    + +

    6.3  Service Load-Balancing

    - -

    6.3.1  Domain Load-Balancing Algorithm

    + +

    6.3.1  Domain Load-Balancing Algorithm

    ejabberd includes an algorithm to load balance the components that are plugged on an ejabberd cluster. It means that you can plug one or several instances of the same component on each ejabberd cluster and that the traffic will be automatically distributed.

    The default distribution algorithm try to deliver to a local instance of a component. If several local instances are available, one instance is chosen randomly. If no instance is available locally, one instance is chosen randomly among the remote component instances.

    If you need a different behaviour, you can change the load balancing behaviour with the option domain_balancing. The syntax of the option is the following:

    domain_balancing: BalancingCriteria

    Several balancing criteria are available:

    If the value corresponding to the criteria is the same, the same component instance in the cluster will be used.

    - -

    6.3.2  Load-Balancing Buckets

    + +

    6.3.2  Load-Balancing Buckets

    When there is a risk of failure for a given component, domain balancing can cause service trouble. If one component is failing the service will not work correctly unless the sessions are rebalanced.

    In this case, it is best to limit the problem to the sessions handled by the failing component. This is what the domain_balancing_component_number option does, making the load balancing algorithm not dynamic, but sticky on a fix number of component instances.

    The syntax is:

    domain_balancing_component_number: Number

    - -

    Chapter 7  Debugging

    + +

    Chapter 7  Debugging

    - -

    7.1  Log Files

    An ejabberd node writes two log files: + +

    7.1  Log Files

    An ejabberd node writes three log files:

    ejabberd.log
    is the ejabberd service log, with the messages reported by ejabberd code -
    erlang.log
    is the Erlang/OTP system log, with the messages reported by Erlang/OTP using SASL (System Architecture Support Libraries) +
    error.log
    is the file accumulating error messages from ejabberd.log +
    crash.log
    is the Erlang/OTP log, with the crash messages reported by Erlang/OTP using SASL (System Architecture Support Libraries)

    The option loglevel modifies the verbosity of the file ejabberd.log. The syntax:

    loglevel: Level
    The standard form to set a global log level. @@ -4928,20 +5011,49 @@ domain.

    For example, the default configuration is: 

    loglevel: 4
-

    The log files grow continually, so it is recommended to rotate them periodically. -To rotate the log files, rename the files and then reopen them. +

    Option log_rate_limit is useful if you want to protect the logging +mechanism from being overloaded by excessive amount of log messages. +The syntax is: +

    +log_rate_limit: N
    Where N is a maximum number of log messages per second. +The default value is 100. +

    +When the limit is reached the similar warning message is logged: +

    lager_error_logger_h dropped 800 messages in the last second that exceeded the limit of 100 messages/sec
+

    By default ejabberd rotates the log files when they get grown above a certain size. +The exact value is controlled by log_rotate_size option. +The syntax is: +

    +log_rotate_size: N
    Where N is the maximum size of a log file in bytes. +The default value is 10485760 (10Mb). +

    ejabberd can also rotates the log files at given date interval. +The exact value is controlled by log_rotate_date option. +The syntax is: +

    +log_rotate_date: D
    Where D is a string with syntax is taken from the syntax newsyslog uses in newsyslog.conf. +The default value is "" (no rotation triggered by date). +

    However, you can rotate the log files manually. +For doing this, set log_rotate_size option to 0 and log_rotate_date +to empty list, then, when you need to rotate the files, rename and then reopen them. The ejabberdctl command reopen-log (please refer to section 4.1.1) reopens the log files, -and also renames the old ones if you didn’t rename them.

    - -

    7.2  Debug Console

    The Debug Console is an Erlang shell attached to an already running ejabberd server. +and also renames the old ones if you didn’t rename them.

    The option log_rotate_count defines the number of rotated files to keep +by reopen-log command. +Every such file has a numeric suffix. The exact format is: +

    +log_rotate_count: N
    The default value is 1, +which means only ejabberd.log.0, error.log.0 +and crash.log.0 will be kept. +

    + +

    7.2  Debug Console

    The Debug Console is an Erlang shell attached to an already running ejabberd server. With this Erlang shell, an experienced administrator can perform complex tasks.

    This shell gives complete control over the ejabberd server, so it is important to use it with extremely care. There are some simple and safe examples in the article Interconnecting Erlang Nodes

    To exit the shell, close the window or press the keys: control+c control+c.

    - -

    7.3  Watchdog Alerts

    + +

    7.3  Watchdog Alerts

    ejabberd includes a watchdog mechanism that may be useful to developers when troubleshooting a problem related to memory usage. If a process in the ejabberd server consumes more memory than the configured threshold, @@ -4963,8 +5075,8 @@ watchdog_large_heap: 30000000 To remove all watchdog admins, set the option with an empty list: 

    watchdog_admins: []

    - -

    Appendix A  Internationalization and Localization

    + +

    Appendix A  Internationalization and Localization

    The source code of ejabberd supports localization. The translators can edit the gettext .po files @@ -4999,11 +5111,11 @@ HTTP header ‘Accept-Language: ru’

    - -

    Appendix B  Release Notes

    + +

    Appendix B  Release Notes

    Release notes are available from ejabberd Home Page

    - -

    Appendix C  Acknowledgements

    Thanks to all people who contributed to this guide: + +

    Appendix C  Acknowledgements

    Thanks to all people who contributed to this guide:

    - -

    Appendix D  Copyright Information

    Ejabberd Installation and Operation Guide.
    + +

    Appendix D  Copyright Information

    Ejabberd Installation and Operation Guide.
    Copyright © 2003 — 2014 ProcessOne

    This document is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 2