Hello,
I setup a rule "If User is XYZ then deny ... else allow all" in my privacy list. The stanza type make no different.
The problem is that on the server jabber.org it's enough to push "apply" and make sure the list with this rule is active, the rule get execute immediately.
Now I make exactly the same rule with the login server jabbim.com.
Nothing happens, the user can still send messages to me or see my status, until I go offfline and online again.
(Jabber.org ejabberd 1.1.4 (with patches), jabbim.com: I don't know)
-Which is the correct way?
-Is this a known problem?
-Is there a fix somewhere?
-Could this be a client problem? (I have test this with miranda and PSI, the same, but who knows...)
I asked this here, because some admins/users from jabber.org and the jabbim.com forum means I should ask here.
Peter
Seems fixed in recent ejabberd versions
Nothing happens, the user can still send messages to me or see my status, until I go offfline and online again.
I tried with ejabberd SVN and Psi 0.11:
-> OK
Default List -> testlist
So it works for me using ejabberd SVN.
(Jabber.org ejabberd 1.1.4 (with patches), jabbim.com: I don't know)
jabber.org advertizes ejabberd 1.1.4. It has some patches to prevent server abuse, but I think they are not related to this issue. jabbim.com uses ejabberd 1.1.2
-Which is the correct way?
I think that the correct behavior is to apply your changes immediately, when you click 'Apply' :)
-Is this a known problem?
-Is there a fix somewhere?
Here you can see the latest changes in mod_privacy:
https://forge.process-one.net/browse/ejabberd/trunk/src/mod_privacy.erl
I don't know if it's a bug in older ejabberd releases, but it seems fixed in recent versions.
-Could this be a client problem? (I have test this with miranda and PSI, the same, but who knows...)
Yes, it could be another reason. But as I said, using Psi 0.11 (the Debian package) and ejabberd development version all worked correctly.
Thanks
Thamks for this info,
I will report it back to the jabbim admins. ;)
Peter