Released versions of ejabberd are available in the ProcessOne ejabberd downloads page:
@@ -681,7 +681,7 @@ Handles incoming s2s connections.
Options: max_stanza_size
Remember that you must also install and enable the module mod_http_bind.
If HTTP Bind is enabled, it will be available at
http://server:port/http-bind/. Be aware that support for HTTP Bind
@@ -727,7 +727,7 @@ interesting to host a web-based Jabber client such as
embedded local web server
or Apache).
If HTTP Polling is enabled, it will be available at
http://server:port/http-poll/. Be aware that support for HTTP Polling
@@ -753,7 +753,7 @@ and you also want mod_http_bind to serve the URIs /http-bind/,
use this option: {request_handlers, [{["a", "b"], mod_foo}, {["http-bind"], mod_http_bind}]}
http://server:port/admin/. Login and password are the username a
password of one of the registered users who are granted access by the
‘configure’ access rule.
Appendix A provides more details about internationalization and localization.
Some ejabberd modules can be configured to require a CAPTCHA challenge on certain actions. -If the client does not support CAPTCHA Forms (XEP-0158), +If the client does not support CAPTCHA Forms (XEP-0158), a web link is provided so the user can fill the challenge in a web browser.
An example script is provided that generates the image using ImageMagick’s Convert program.
The configurable options are:
Example configuration:
ejabberd is able to act as a stand-alone STUN server (RFC 5389). Currently only Binding usage -is supported. In that role ejabberd helps clients with Jingle ICE (XEP-0176) support to discover their external addresses and ports.
You should configure ejabberd_stun listening module as described in 3.1.3 section. +is supported. In that role ejabberd helps clients with Jingle ICE (XEP-0176) support to discover their external addresses and ports.
You should configure ejabberd_stun listening module as described in 3.1.3 section. If certfile option is defined, ejabberd multiplexes TCP and TLS over TCP connections on the same port. Obviously, certfile option is defined for tcp only. Note however that TCP or TLS over TCP @@ -1663,7 +1663,7 @@ user’s part of a JID. For example, "%u@example.org". The default value is "%u".
The following table lists all modules included in ejabberd.
- Module Feature Dependencies + mod_adhoc Ad-Hoc Commands (XEP-0050) mod_adhoc Ad-Hoc Commands (XEP-0050) - mod_announce Manage announcements recommends mod_adhoc + mod_caps Entity Capabilities (XEP-0115) mod_caps Entity Capabilities (XEP-0115) - mod_configure Server configuration using Ad-Hoc mod_adhoc + mod_disco Service Discovery (XEP-0030) mod_disco Service Discovery (XEP-0030) mod_echo Echoes Jabber packets - mod_irc IRC transport - mod_last Last Activity (XEP-0012) - mod_last_odbc Last Activity (XEP-0012) supported DB (*) + mod_muc Multi-User Chat (XEP-0045) + mod_last Last Activity (XEP-0012) + mod_last_odbc Last Activity (XEP-0012) supported DB (*) mod_muc Multi-User Chat (XEP-0045) - mod_muc_log Multi-User Chat room logging mod_muc - mod_offline Offline message storage (XEP-0160) - mod_offline_odbc Offline message storage (XEP-0160) supported DB (*) + mod_ping XMPP Ping and periodic keepalives (XEP-0199) + mod_offline Offline message storage (XEP-0160) + mod_offline_odbc Offline message storage (XEP-0160) supported DB (*) mod_ping XMPP Ping and periodic keepalives (XEP-0199) mod_privacy Blocking Communication (XMPP IM) - mod_privacy_odbc Blocking Communication (XMPP IM) supported DB (*) - mod_private Private XML Storage (XEP-0049) - mod_private_odbc Private XML Storage (XEP-0049) supported DB (*) - mod_proxy65 SOCKS5 Bytestreams (XEP-0065) - mod_pubsub Pub-Sub (XEP-0060), PEP (XEP-0163) mod_caps + mod_register In-Band Registration (XEP-0077) + mod_private Private XML Storage (XEP-0049) + mod_private_odbc Private XML Storage (XEP-0049) supported DB (*) + mod_proxy65 SOCKS5 Bytestreams (XEP-0065) + mod_pubsub Pub-Sub (XEP-0060), PEP (XEP-0163) mod_caps mod_register In-Band Registration (XEP-0077) mod_roster Roster management (XMPP IM) mod_roster_odbc Roster management (XMPP IM) supported DB (*) mod_service_log Copy user messages to logger service mod_shared_roster Shared roster management mod_roster or - mod_roster_odbc - mod_stats Statistics Gathering (XEP-0039) - mod_time Entity Time (XEP-0202) - mod_vcard vcard-temp (XEP-0054) - mod_vcard_ldap vcard-temp (XEP-0054) LDAP server - mod_vcard_odbc vcard-temp (XEP-0054) supported DB (*) + mod_version Software Version (XEP-0092) + mod_stats Statistics Gathering (XEP-0039) + mod_time Entity Time (XEP-0202) + mod_vcard vcard-temp (XEP-0054) + mod_vcard_ldap vcard-temp (XEP-0054) LDAP server + mod_vcard_odbc vcard-temp (XEP-0054) supported DB (*) mod_version Software Version (XEP-0092)
This module adds support for Service Discovery (XEP-0030). With +
This module adds support for Service Discovery (XEP-0030). With this module enabled, services on your server can be discovered by Jabber clients. Note that ejabberd has no modules with support -for the superseded Jabber Browsing (XEP-0011) and Agent Information -(XEP-0094). Accordingly, Jabber clients need to have support for +for the superseded Jabber Browsing (XEP-0011) and Agent Information +(XEP-0094). Accordingly, Jabber clients need to have support for the newer Service Discovery protocol if you want them be able to discover the services you offer.
Options:
This module implements XMPP over Bosh (formerly known as HTTP Binding) -as defined in XEP-0124 and XEP-0206. +as defined in XEP-0124 and XEP-0206. It extends ejabberd’s built in HTTP service with a configurable resource at which this service will be hosted.
To use HTTP-Binding, enable the module:
{modules,
@@ -2209,7 +2209,7 @@ servers.End user information:
This module adds support for Last Activity (XEP-0012). It can be used to +
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 ejabberd server.
Options: @@ -2273,7 +2273,7 @@ connected user was last active on the server, or to query the uptime of the the processing discipline for Last activity (jabber:iq:last) IQ queries (see section 3.3.2).
This module provides a Multi-User Chat (XEP-0045) service. +
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:
<a href="/">Home</a>.
]}.
This module implements offline message storage (XEP-0160). +
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 online again. Thus it is very similar to how email works. Note that @@ -2648,7 +2648,7 @@ and all the other users up to 100. ]}.
This module implements support for XMPP Ping (XEP-0199) and periodic keepalives. +
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:
Options:
This module adds support for Private XML Storage (XEP-0049): +
This module adds support for Private XML Storage (XEP-0049):
Using this method, Jabber entities can store private data on the server and retrieve it whenever necessary. The data stored might be anything, as long as it is valid XML. One typical usage for this namespace is the server-side storage -of client-specific preferences; another is Bookmark Storage (XEP-0048). +of client-specific preferences; another is Bookmark Storage (XEP-0048).
Options:
This module implements SOCKS5 Bytestreams (XEP-0065). +
This module implements SOCKS5 Bytestreams (XEP-0065). It allows ejabberd to act as a file transfer proxy between two XMPP clients.
Options:
This module offers a Publish-Subscribe Service (XEP-0060). +
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) +The plugin that implements PEP (Personal Eventing via Pubsub) (XEP-0163) is enabled in the default ejabberd configuration file, and it requires mod_caps.
Options:
This module adds support for In-Band Registration (XEP-0077). This protocol +
This module adds support for In-Band Registration (XEP-0077). This protocol enables end users to use a Jabber client to:
This module implements roster management as defined in -RFC 3921: XMPP IM. -It also supports Roster Versioning (XEP-0237).
Options: +RFC 3921: XMPP IM. +It also supports Roster Versioning (XEP-0237).
Options:
This module adds support for Statistics Gathering (XEP-0039). This protocol +
This module adds support for Statistics Gathering (XEP-0039). This protocol allows you to retrieve next statistics from your ejabberd deployment:
This module features support for Entity Time (XEP-0202). By using this XEP, +
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:
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 +other users vCards, as defined in vcard-temp (XEP-0054). The module also implements an uncomplicated Jabber User Directory based on the vCards of these users. Moreover, it enables the server to send its vCard when queried.
Options:
This module implements Software Version (XEP-0092). Consequently, it +
This module implements Software Version (XEP-0092). Consequently, it answers ejabberd’s version when queried.
Options:
If you enable mod_configure and mod_adhoc, you can perform several administrative tasks in ejabberd with a Jabber client. -The client must support Ad-Hoc Commands (XEP-0050), +The client must support Ad-Hoc Commands (XEP-0050), and you must login in the Jabber server with an account with proper privileges.
ejabberd uses the distributed Mnesia database. diff --git a/doc/guide.tex b/doc/guide.tex index 9b291b688..aba77c4ad 100644 --- a/doc/guide.tex +++ b/doc/guide.tex @@ -170,7 +170,7 @@ ejabberd Development Team \gdef\ahrefurl#1{\href{#1}{\texttt{#1}}} \gdef\footahref#1#2{#2\footnote{\href{#1}{\texttt{#1}}}} \end{latexonly} -\newcommand{\txepref}[2]{\footahref{http://www.xmpp.org/extensions/xep-#1.html}{#2}} +\newcommand{\txepref}[2]{\footahref{http://xmpp.org/extensions/xep-#1.html}{#2}} \newcommand{\xepref}[1]{\txepref{#1}{XEP-#1}} \begin{document} @@ -912,7 +912,7 @@ This is a detailed description of each option allowed by the listening modules: commonly on port 5223 for client-to-server communications. But this method is nowadays deprecated and not recommended. The preferable encryption method is STARTTLS on port 5222, as defined - \footahref{http://www.xmpp.org/specs/rfc3920.html\#tls}{RFC 3920: XMPP Core}, + \footahref{http://xmpp.org/specs/rfc3920.html\#tls}{RFC 3920: XMPP Core}, which can be enabled in \ejabberd{} with the option \term{starttls}. If this option is set, you should also set the \option{certfile} option. \titem{web\_admin} \ind{options!web\_admin}\ind{web admin}This option @@ -2223,9 +2223,9 @@ You can authenticate users against an LDAP directory. Available options are: user's part of a JID. For example, \term{"\%u@example.org"}. The default value is \term{"\%u"}. \end{description} - \titem{ldap\_filter}\ind{options!ldap\_filter}\ind{protocols!RFC 2254: The - String Representation of LDAP Search Filters} - \footahref{http://www.faqs.org/rfcs/rfc2254.html}{RFC 2254} LDAP filter. The + \titem{ldap\_filter}\ind{options!ldap\_filter}\ind{protocols!RFC 4515: + LDAP String Representation of Search Filters} + \footahref{http://tools.ietf.org/html/rfc4515}{RFC 4515} LDAP filter. The default is \term{none}. Example: \term{"(\&(objectClass=shadowAccount)(memberOf=Jabber Users))"}. Please, do not forget to close brackets and do not use superfluous whitespaces. Also you @@ -3237,7 +3237,7 @@ Features: author, subject and configuration. \item \ind{protocols!RFC 5122: Internationalized Resource Identifiers (IRIs) and Uniform Resource Identifiers (URIs) for the Extensible Messaging and Presence Protocol (XMPP)} The room JID in the generated HTML is a link to join the room (using - \footahref{http://www.xmpp.org/rfcs/rfc5122.html}{XMPP URI}). + \footahref{http://xmpp.org/rfcs/rfc5122.html}{XMPP URI}). \item Subject and room configuration changes are tracked and displayed. \item Joins, leaves, nick changes, kicks, bans and `/me' are tracked and displayed, including the reason if available. @@ -3458,7 +3458,7 @@ their \Jabber{} client, they will be able to: \item Allowing or blocking all communications based on JID, group, or subscription type (or globally). \end{itemize} -(from \ahrefurl{http://www.xmpp.org/specs/rfc3921.html\#privacy}) +(from \ahrefurl{http://xmpp.org/specs/rfc3921.html\#privacy}) \end{quote} Options: @@ -3695,7 +3695,7 @@ Also define a registration timeout of one hour: \ind{modules!\modroster{}}\ind{roster management}\ind{protocols!RFC 3921: XMPP IM} This module implements roster management as defined in -\footahref{http://www.xmpp.org/specs/rfc3921.html\#roster}{RFC 3921: XMPP IM}. +\footahref{http://xmpp.org/specs/rfc3921.html\#roster}{RFC 3921: XMPP IM}. It also supports Roster Versioning (\xepref{0237}). Options: @@ -4026,7 +4026,7 @@ consists of the following \modvcardldap{}-specific options: set the table that maps LDAP attributes to vCard fields. The format is: \term{[{Name\_of\_vCard\_field, Pattern, List\_of\_LDAP\_attributes}, ...]}.\ind{protocols!RFC 2426: vCard MIME Directory Profile} \term{Name\_of\_vcard\_field} is the type name of the vCard as defined in - \footahref{http://www.ietf.org/rfc/rfc2426.txt}{RFC 2426}. \term{Pattern} is a + \footahref{http://tools.ietf.org/html/rfc2426}{RFC 2426}. \term{Pattern} is a string which contains pattern variables \term{"\%u"}, \term{"\%d"} or \term{"\%s"}. \term{List\_of\_LDAP\_attributes} is the list containing LDAP attributes. The pattern variables \term{"\%s"} will be sequentially replaced diff --git a/doc/introduction.tex b/doc/introduction.tex index 1991c93ec..7cbfe625e 100644 --- a/doc/introduction.tex +++ b/doc/introduction.tex @@ -8,7 +8,7 @@ Joeri} %ejabberd is a free and open source instant messaging server written in Erlang. ejabberd is cross-platform, distributed, fault-tolerant, and based on open standards to achieve real-time communication (Jabber/XMPP). -\ejabberd{} is a \marking{free and open source} instant messaging server written in \footahref{http://www.erlang.org/}{Erlang}. +\ejabberd{} is a \marking{free and open source} instant messaging server written in \footahref{http://www.erlang.org/}{Erlang/OTP}. \ejabberd{} is \marking{cross-platform}, distributed, fault-tolerant, and based on open standards to achieve real-time communication.