aboutsummaryrefslogtreecommitdiff
path: root/doc/guide.html
diff options
context:
space:
mode:
authorBadlop <badlop@process-one.net>2010-01-12 23:57:44 +0000
committerBadlop <badlop@process-one.net>2010-01-12 23:57:44 +0000
commit855d42718295172d88edc917c2cab822f7ab1fae (patch)
treea7e0cf87528b1bf7c5340ced74618d1c328e3db3 /doc/guide.html
parentCheck for Effective GID EGID in ejabberdctl (thanks to Rustam Aliyev)(EJAB-1160) (diff)
Fix explanation of access_max_user_messages.
SVN Revision: 2895
Diffstat (limited to 'doc/guide.html')
-rw-r--r--doc/guide.html2
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/guide.html b/doc/guide.html
index eabd4312e..f5a39904a 100644
--- a/doc/guide.html
+++ b/doc/guide.html
@@ -2636,7 +2636,7 @@ 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
<TT>ejabberdctl</TT> has a command to delete expired messages
(see section&#XA0;<A HREF="#ejabberdctl">4.1</A>).</P><DL CLASS="description"><DT CLASS="dt-description">
-<B><TT>{access_max_user_messages, Number}</TT></B></DT><DD CLASS="dd-description">
+<B><TT>{access_max_user_messages, AccessName}</TT></B></DT><DD CLASS="dd-description">
This option defines which access rule will be enforced to limit
the maximum number of offline messages that a user can have (quota).
When a user has too many offline messages, any new messages that he receive are discarded,