blocking not working with ejabberd 2.1.10

Hi,

Maybe I just do not understand how it is supposed to work yet it seems to me that blocking is not working with ejabberd 2.1.10
and pidgin 2.10.1 (nor with spark 2.6.3)
And I do not see 'jabber:iq:privacy' in discovery either.

I have {mod_blocking,[]}, and {mod_privacy_odbc,[]}, in ejabberd.cfg but when I try to block user I get:

in Pidgin:

(03:06:59) jabber: Sending (ssl) (me@domain.com/AMC): <iq type='set' id='purplefc5c17a5'><block xmlns='urn:xmpp:blocking'><item jid='bad@user.com'/></block></iq>
(03:06:59) jabber: Recv (ssl)(163): <iq from='me@domain.com' to='me@domain.com/AMC' id='push416017944' type='set'><query xmlns='jabber:iq:privacy'><list name='Blocked contacts'/></query></iq>
(03:06:59) jabber: Unhandled IQ with id push416017944
(03:06:59) jabber: Sending (ssl) (me@domain.com/AMC): <iq xmlns='jabber:client' id='push416017944' to='me@domain.com' type='error'><query xmlns='jabber:iq:privacy'><list name='Blocked contacts'/></query><error type='cancel' code='501'><feature-not-implemented xmlns='urn:ietf:params:xml:ns:xmpp-stanzas'/></error></iq>
(03:06:59) jabber: Recv (ssl)(155): <iq from='me@domain.com' to='me@domain.com/AMC' id='push' type='set'><block xmlns='urn:xmpp:blocking'><item jid='bad@user.com'/></block></iq>
(03:06:59) jabber: Sending (ssl) (me@domain.com/AMC): <iq type='result' id='push'/>
(03:06:59) jabber: Recv (ssl)(91): <iq from='me@domain.com' to='me@domain.com/AMC' id='purplefc5c17a5' type='result'/>
(03:06:59) jabber: Unhandled IQ with id purplefc5c17a5

When I manually send:

<iq from='me@domain.com/AMC' type='set' id='id1public'>
   <query xmlns='jabber:iq:privacy'>
      <list name='public'>
         <item action='allow' order='1'></item>
      </list>
   </query>
</iq>

I get same error (feature-not-implemented) yet list is created in MySQL

mysql> select * from privacy_list;
+----------+--------+----+---------------------+
| username | name   | id | created_at          |
+----------+--------+----+---------------------+
| me       | public |  1 | 2012-02-15 03:27:15 |
+----------+--------+----+---------------------+
1 row in set (0.00 sec)

this same goes for deleting.

and Spark says : Privacy lists are not supported by server.

What am I doing wrong ? Is it client's problem ? Or misconfiguration on my part ?

Thank you for your help.

Regards,

Michal

kopecnym wrote: Maybe I just

kopecnym wrote:

Maybe I just do not understand how it is supposed to work yet it seems to me that blocking is not working with ejabberd 2.1.10
and pidgin 2.10.1 (nor with spark 2.6.3)

Why do you say the Blocking feature does not work?

kopecnym wrote:

And I do not see 'jabber:iq:privacy' in discovery either.

For some unknown reason, ejabberd doesn't announce that feature. It announces urn:xmpp:blocking only.

kopecnym wrote:
(03:06:59) jabber: Sending (ssl) (me@domain.com/AMC): <iq type='set' id='purplefc5c17a5'><block xmlns='urn:xmpp:blocking'><item jid='bad@user.com'/></block></iq>
(03:06:59) jabber: Recv (ssl)(163): <iq from='me@domain.com' to='me@domain.com/AMC' id='push416017944' type='set'><query xmlns='jabber:iq:privacy'><list name='Blocked contacts'/></query></iq>
(03:06:59) jabber: Unhandled IQ with id push416017944
(03:06:59) jabber: Sending (ssl) (me@domain.com/AMC): <iq xmlns='jabber:client' id='push416017944' to='me@domain.com' type='error'><query xmlns='jabber:iq:privacy'><list name='Blocked contacts'/></query><error type='cancel' code='501'><feature-not-implemented xmlns='urn:ietf:params:xml:ns:xmpp-stanzas'/></error></iq>

So your client sends the query, ejabberd replies that all is correct. Then your client sends a feature-not-implemented. Maybe your client gets confused.

I tried with ejabberd 2.1.10 and Pidgin 2.10.0. I see in the logs the same that you, and the feature works correctly: when i block a contact, I don't receive messages that he sends me.

Thank you for your reply.

Thank you for your reply.

When I block - for example gmail user - I will not receive messages from him but he keeps seeing me online - I thought that blocking includes presence as well. (that's why I even did not try to send messages - when both sides see each other online seems rude to ignore messages)

Best regards,

Michal

Syndicate content