24
1
mirror of https://github.com/processone/ejabberd.git synced 2024-06-16 22:05:29 +02:00

Fix explanation of access_max_user_messages.

SVN Revision: 2897
This commit is contained in:
Badlop 2010-01-13 00:00:11 +00:00
parent 82cd0adb79
commit 4639c0faf0
2 changed files with 2 additions and 2 deletions

View File

@ -2556,7 +2556,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,

View File

@ -3293,7 +3293,7 @@ online again. Thus it is very similar to how email works. Note that
(see section~\ref{ejabberdctl}).
\begin{description}
\titem{\{access\_max\_user\_messages, Number\}}\ind{options!access\_max\_user\_messages}
\titem{\{access\_max\_user\_messages, AccessName\}}\ind{options!access\_max\_user\_messages}
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,