Description

The jabberbot sends XMPP-messages with the message-type message. According to the XMPP RFC this is an illegal message-type:

Types of Message

[...] If included, the 'type' attribute MUST have one of the following values:

 chat [...]
 error [...]
 groupchat [...]
 headline [...]
 normal [...]

This bug crops up if a jabber-client does not show messages with an unknown message-type. An example is the Pidgin instant messenger (former Gaim). Note that this behaviour is also a bug, the RFC states it should use normal then. In a nutshell, the bug is present because both the jabberbot and the jabber-client are not RFC compliant .

See also: Pidgin Bugreport #7837

Steps to reproduce

1. Edit some page you have subscribed to via Jabber as another user (or anonymously)
2. Look at the raw XMPP XML message in your jabber-client (e.g. there's a XMPP-console plugin for Pidgin)

Component selection

• jabberbot

Details

Workaround

Use a RFC compliant jabber-client.

Patch

A trivial patch to fix this problem .

moin_jabberbot_rfc_compliant_message_type.patch

Discussion

Plan

• Priority:
• Assigned to:
• Status:

CategoryMoinMoinBug