Good day,
announcments are not working ejabberd-1.1.1 + active directory + freebsd
A part of config:
==start==
{hosts, ["10.0.0.1"]}.
{access, announce, [{allow, all}]}.
{mod_announce, [{access, announce}]},
==end=
seens to be normal.
I am trying to send message to jid "10.0.0.1/announce/online", but doesn't work.
announcments are not to see through "finding out of servers"
The whole config is here:
Where could be the problem? Maybe somebody meet it?
Looking for ejabberd docs?
To access the most up-to-date ejabberd documentation, please visit docs.ejabberd.im »
mod_announce
Submitted by wiznet1 on Mon, 2006-11-20 09:43
Check ejabberd log files
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.
any way of external logging?
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
Try override_acls.
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
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.