Hi,
I am using ejabberd to connect thousands of clients on my server. I want the clients to have access to manage their privacy list, in other words block/unblock contacts on their rosters. I have enabled mod_privacy but somehow its not working. Can someone please assist me on how to properly configure mod_privacy ?
Any suggestions on how to enable this "block/unblock" feature on server so that it can be controlled with XMPP's XEP-0191.
Thanks,
DH
I have the same problem, too
Hi, i'm using ejabberd with the default configuration, except for database. i'm using MySql, so i renamed the module "mod_privacy" in "mod_privacy_odbc" and in the MySql db i created the table for that.
But i'm not able to block user. for example, i'm using Pidgin as client, i connect to my ejabberd server, and then i try to make the operation "block user X", but Pidgin tell me "Server doesn't support block".
in my configuration file, i have only this row:
{mod_privacy_odbc, []},
maybe i have to configure mod_privacy in another way?
can someone help us with this issue?
i think that it's an important feature for an instant messaging server.
thank you,
P.
Re
There are two protocols for that feature, and Pidgin implements the one that ejabberd does not support.
Privacy lists (XEP-0016) supported by: Gajim, Jabbim, Psi, Tkabber.
Com. Blocking (XEP-0191) supported by: Pidgin.
The good news are that you can download an experimental patch and recompile ejabberd to get the feature:
Thank you for reply
so do you think this patch is something that you want to improve and introduce in the next releases of ejabberd?
thank you again,
P.
Patch was committed
Yes, I was working on the patch already. In fact, I've just committed it to ejabberd git, and will be included in ejabberd 2.1.7, which will be released probably in the first days of June.
Hi, When I was trying to
Hi, When I was trying to block some one, but it didn't work, here is the xml sent and received, thanks for the help.
SENT:
<iq xmlns='jabber:client' from='222@hzs-t61-elou/mylife-localhost-100' id='4' type='set'><query xmlns='jabber:iq:privacy'><list name='public'><item action='deny' order='1' type='jid' value='22@hzs-t61-elou'/></list></query></iq>RECEIVED:
<iq from='222@hzs-t61-elou' id='push4191354387' to='222@hzs-t61-elou/mylife-localhost-100' type='set' xml:lang='en'><query xmlns='jabber:iq:privacy'><list name='public'/></query></iq>
<iq from='222@hzs-t61-elou' id='4' to='222@hzs-t61-elou/mylife-localhost-100' type='result' xml:lang='en'/>
I have read the xmpp extension xep-0016, it seems I was doing the correct job, but it didn't work, these 2 people can still see each other's presence. Any idea?
BY the way, why the privacy puch didn't contain the item? IT's same with the protocol definition, I can't under stand this too much.
Hi, When I was trying to
Hi, When I was trying to block some one, but it didn't work, here is the xml sent and received, thanks for the help.
SENT:
<iq xmlns='jabber:client' from='222@hzs-t61-elou/mylife-localhost-100' id='4' type='set'><query xmlns='jabber:iq:privacy'><list name='public'><item action='deny' order='1' type='jid' value='22@hzs-t61-elou'/></list></query></iq>RECEIVED:
<iq from='222@hzs-t61-elou' id='push4191354387' to='222@hzs-t61-elou/mylife-localhost-100' type='set' xml:lang='en'><query xmlns='jabber:iq:privacy'><list name='public'/></query></iq><iq from='222@hzs-t61-elou' id='4' to='222@hzs-t61-elou/mylife-localhost-100' type='result' xml:lang='en'/>
I have read the xmpp extension xep-0016, it seems I was doing the correct job, but it didn't work, these 2 people can still see each other's presence. Any idea?
BY the way, why the privacy puch didn't contain the item? IT's same with the protocol definition, I can't under stand this too much.
When a privacy list is
When a privacy list is modified, the server notifies all resources about this change (it tells each connected client of this user: hey, the privacy list "xyz" of this user was changed). A client may then wish to get this list, or it may not. If and only if it wish, it will ask server with the appropriate "get". Otherwise, no unwanted traffic is generated.
User may have more than one privacy list, and (s)he may set only one privacy list active for each resource. Probably you haven't set your "public" privacy list active for your resource.
Thanks, Mike. So we need to
Thanks, Mike.
So we need to set the "public" list as the active list, I think.
Generally speaking, this operation was done at what time? after getting roster?
http://xmpp.org/extensions/xe
I suppose that there's no restrictions regarding the order of this operation. However, the default privacy list (if set) will be active until a list will be set active for the session.
I suppose the default privacy
I suppose the default privacy list is the "public" for ejabber, isn't it?
Or should I set it explictly?
I suppose that there's no
I suppose that there's no default.
You can easily check it:
See Examples 1 & 2, where server responds with the list where the default and active lists are specified.
You seem to ask questions you could answer yourself by reading relevant documents carefully.
See by Eric Steven Raymond.