ejabberd - Comments for "mod_announce"

Try override_acls.

mfoss — Mon, 20 Nov 2006 21:01:08 +0000

wiznet1 wrote:

how could i log/debug startup events of ejabberd? (modules loaded etc)

On the web admin you can see which modules were loaded: Virtual Hosts -> your host -> Nodes -> your node -> Modules

wiznet1 wrote:

anyway why its not visible in services? and announce/all isnt work too => looks like not auth trouble

If the user has the right to send announce messages, the option should be listed on Service Directory (works on Psi 0.10). If the client also supports Ad-hoc commands, it will be able to send messages using that method (instead of the old JIDs announce/all..., works on Tkabber 0.9.9).

Using Tkabber 0.9.9, if I login with a user that has no rights to send announces, when I try to send one, I get this message: 'subject: Error on the authentication (Not allowed)'.

Maybe you made a mistake on the config of ACLs, and ejabberd still remembers it (on the database). To make sure ejabberd forgets all old ACLs that may be stored on database, uncomment at beginning of ejabberd.cfg the line 'override_acls.' and restart ejabberd.

any way of external logging?

wiznet1 — Mon, 20 Nov 2006 12:13:25 +0000

i have only ejabberd.log and it seems correct, i.e. no error messages
how could i log/debug startup events of ejabberd? (modules loaded etc)
anyway why its not visible in services? and announce/all isnt work too => looks like not auth trouble

Check ejabberd log files

mfoss — Mon, 20 Nov 2006 11:35:41 +0000

I tried that config using ejabberd 1.1.2 and internal auth: it works correctly. And it seems announce/online does not query AD, just ejabberd database. Check ejabberd log files, maybe some error message appears.

Try announce/all too, to see if that one works. When using LDAP auth, ejabberd asks LDAP server which users are registered. Looking at the contributed AD patch, the required functions seem to be implemented.