What steps will reproduce the problem?
1. I block JIDs through Gajim and Conversations (MattJ said this might make a differences).
2. No matter where a block the JIDs messages are still delivered. Very annoying as all these JIDs are spammers and they use a JID more than one time. So blocking kinda makes sense anyway.
What is the expected output? What do you see instead?
No messages from blocked JIDs.
What version of the product are you using? On what operating system?
Prosody 1nightly271-1~jessie (just upgraded to 1nightly273-1~jessie) on Debian jessie stable plus some jessie-backports on amd64.
Please provide any additional information below.
Active modules are:
Reproduced at first, but then I noticed that you have to enable the list by checking the 'Active on each startup' checkbox.
Please verify that at least one of the two checkboxes in the list editing dialog is checked.
You can also check by looking at if your stored privacy list data contains a "default" top level key.
Hi Zash, with some help I found the setting in Gajim. And you were right, nothing was enabled on startup. Another interesting thing is that I have two lists. One is named "blocklist" and the other "block". Only one list can be loaded.
MattJ said this is because of the use of XEP-0016 (Gajim) and XEP-0191 (Conversations) and a transformation Prosody is performing for XEP-0016 blacklists. I will open a ticket for Gajim (if there is not already one) and ask for XEP-0191 which MattJ said is the better choice.
I'm closing this. I believe the issue in Gajim has been resolved.