Opened 11 years ago

Closed 11 years ago

Last modified 11 years ago

#6364 closed task (wontfix)

XMPP Message Error

Reported by: hcpaj Owned by: nwalp
Milestone: Component: XMPP
Version: 2.4.3 Keywords: Code 403
Cc:

Description

I currently use Openfire/Spark? for our company, but have been testing Pidgin as a client option because it seems a bit cleaner and uses less than half the resources Spark does. Set up went smoothly and I connected to the server fine. I can get my groups and user lists and chat works.

I was testing the chat/conference room functionality and it found the room fine (that I set up using admin panel on Openfire). When I send a message from my Spark client, it goes through fine, but when I send a message from Pidgin, I get "XMPP Message Error. Message delivery to (room@…) failed: (Code 403)". This is with no added plugins and I tried with and without Spark running.

I recreated it for the debug log (I replaced server name):

--- Pidgin Debug Log : 7/17/2008 11:45:50 AM (11:45:31) jabber: Recv (ssl)(204): <message id="q2Suo-118" to="adm@server/server" type="groupchat" from="room@…/James"><body>test</body><x xmlns="jabber:x:event"><offline/><delivered/><displayed/><composing/></x></message>

(11:45:36) jabber: Sending (ssl): <message type='groupchat' id='purpleef981b22' to='room@…'><body>test</body><html xmlns='http://jabber.org/protocol/xhtml-im'><body xmlns='http://www.w3.org/1999/xhtml'>test</body></html></message>

(11:45:36) jabber: Recv (ssl)(328): <message type="error" id="purpleef981b22" to="adm@server/server" from="room@…"><body>test</body><html xmlns="http://jabber.org/protocol/xhtml-im"><body xmlns="http://www.w3.org/1999/xhtml">test</body></html><error code="403" type="auth"><forbidden xmlns="urn:ietf:params:xml:ns:xmpp-stanzas"/></error></message> ---

Also, I don't suppose there is any way to limit which protocols are available for users?

Thanks

Change History (6)

comment:1 Changed 11 years ago by deryni

  • pending changed from 0 to 1

You can limit which protocols are available by removing the plugins for the protocols you don't want available. However, all the user would need to do is reinstall those plugins to gain access to those protocols. You would need a custom build of pidgin without plugin support and with just the desired protocols statically compiled to prevent it entirely.

Is the room set up to disallow xhtml-im formatted messages? Is that user not allowed to speak in that room? There isn't anything specific in the returned error message so without more information I don't think there is much more I can say about it.

comment:2 Changed 11 years ago by hcpaj

  • pending changed from 1 to 0

'doh I forgot to add the user to the room members. I knew I was forgetting something...

thx

comment:3 Changed 11 years ago by deryni

  • pending changed from 0 to 1

So can I close this ticket then?

comment:4 Changed 11 years ago by hcpaj

  • pending changed from 1 to 0

yes, thank you

comment:5 Changed 11 years ago by datallah

  • Resolution set to wontfix
  • Status changed from new to closed

comment:6 Changed 11 years ago by datallah

Sorry, I meant to close it as "Invalid" instead of "WontFix?"

Note: See TracTickets for help on using tickets.
All information, including names and email addresses, entered onto this website or sent to mailing lists affiliated with this website will be public. Do not post confidential information, especially passwords!