On 30.05.2006 13:23 (+0100), Remko Troncon wrote:
> AFAIK, the RFC states that, if a client has not set an active list
> during its session, the default list is used. The ejabberd
> implementation automatically sets the default list as active if the
> client doesn't specify an active list. It sounds to me like you have
> a buggy server (that is, if you followed the correct procedure of
> setting the default list).
This was my XML input:
<iq type='set'>
<query xmlns='jabber:iq:privacy'>
<list name='my-blocks'>
<item type='jid' value='[EMAIL PROTECTED]' action='deny'
order='1'/>
<item type='jid'
value='[EMAIL PROTECTED]' action='deny'
order='2'/>
</list>
</query>
</iq>
<iq type='set'>
<query xmlns='jabber:iq:privacy'>
<default name='my-blocks'/>
<active name='my-blocks'/>
</query>
</iq>
The server reportet no errors and enumerating and retrieving the list
did also work. But in the next session, it's no longer active (but still
present).
--
Yves Goergen "LonelyPixel" <[EMAIL PROTECTED]>
http://beta.unclassified.de – My web laboratory.
