From 44e0a17d808be61578ed810033380a9ec584973d Mon Sep 17 00:00:00 2001
From: Badlop
+
@@ -97,26 +83,8 @@ BLOCKQUOTE.figure DIV.center DIV.center HR{display:none;}
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-ejabberd Development Team Contents
To compile ejabberd on a Microsoft Windows system, you need:
The following databases are supported by ejabberd:
The following LDAP servers are tested with ejabberd: @@ -1459,8 +1427,18 @@ default is none. Example: "(&(objectClass=shadowAccount)(memberOf=Jabber Users))". Please, do not forget to close brackets and do not use superfluous whitespaces. Also you must not use ldap_uidattr attribute in filter because this -attribute will be substituted in LDAP filter automatically. -
+attribute will be substituted in LDAP filter automatically.{ldap_local_filter, {notequal, {"accountStatus",["disabled"]}}}. +{ldap_local_filter, {equal, {"accountStatus",["enabled"]}}}. +{ldap_local_filter, undefined}. +
Let’s say ldap.example.org is the name of our LDAP server. We have
users with their passwords in "ou=Users,dc=example,dc=org" directory.
@@ -2168,7 +2146,7 @@ custom CSS file will be used (http://example.com/my.css). Further, the names
of the log files will contain the full date, and there will be no
subdirectories. The log files will be stored in /var/www/muclogs, and the
time zone will be GMT/UTC. Finally, the top link will be
-<a href="http://www.jabber.ru">Jabber.ru</a>
.
+<a href="http://www.jabber.ru/">Jabber.ru</a>
.
{access, muc, [{allow, all}]}. {modules, @@ -2181,7 +2159,7 @@ time zone will be GMT/UTC. Finally, the top link will be {outdir, "/var/www/muclogs"}, {timezone, universal}, {spam_prevention, true}, - {top_link, {"http://www.jabber.ru", "Jabber.ru"}} + {top_link, {"http://www.jabber.ru/", "Jabber.ru"}} ]}, ... ]}. @@ -2428,7 +2406,7 @@ the processing discipline for Roster Management (jabber:iq:roster) IQ q3.3.17 mod_service_log
This module adds support for logging end user packets via a Jabber message auditing service such as -Bandersnatch. All user +Bandersnatch. All user packets are encapsulated in a
<route/>
element and sent to the specified service(s).Options:
- +