Windows version of pidgin 2.5.0 is not recieving messages. XMPP.

Daniel Atallah daniel.atallah at
Fri Aug 22 11:50:09 EDT 2008

On Fri, Aug 22, 2008 at 8:32 AM, David Michal <dvd.mchl at> wrote:
>> Look at the debug log (Help->Debug Window) to see if the message even
>> makes it to Pidgin.
> Ah it's a nice feature this debug window. I haven't noticed it before.
> Anyway, pidgin received the reply message from my bot, but the message
> didn't appear in the chat window.
> (13:26:18) jabber: Sending (ssl): <message type='chat' id='purpleabd63ef1'
> to='dvdmchl-jabworld at'><x
> xmlns='jabber:x:event'><composing/></x><composing
> xmlns=''/></message>
> (13:26:24) jabber: Sending (ssl): <message type='chat' id='purpleabd63ef2'
> to='dvdmchl-jabworld at'><x xmlns='jabber:x:event'/><paused
> xmlns=''/></message>
> (13:26:24) conversation: typed...
> (13:26:27) jabber: Sending (ssl): <message type='chat' id='purpleabd63ef3'
> to='dvdmchl-jabworld at'><x
> xmlns='jabber:x:event'><composing/></x><active
> xmlns=''/><body>help</body><html
> xmlns=''><body
> xmlns=''>help</body></html></message>
> (13:26:27) jabber: Sending (ssl): <message type='chat' id='purpleabd63ef4'
> to='dvdmchl-jabworld at'><x xmlns='jabber:x:event'/><active
> xmlns=''/></message>
> (13:26:30) jabber: Sending (ssl): <iq type='get' id='purpleabd63ef5'><ping
> xmlns='urn:xmpp:ping'/></iq>
> (13:26:30) jabber: Recv (ssl)(232): <iq from='dvd.mchl at'
> to='dvd.mchl at' type='error' id='purpleabd63ef5'><ping
> xmlns='urn:xmpp:ping'/><error code='503' type='cancel'><service-unavailable
> xmlns='urn:ietf:params:xml:ns:xmpp-stanzas'/></error></iq>
> (13:26:34) jabber: Recv (ssl)(338): <message
> from='dvdmchl-jabworld at'
> to='dvd.mchl at' type='chat' id='5'><body>Available commands:
> rot13: Returns passed arguments rot13'ed
> time: Displays current server time
> whoami: Tells you your username
> serverinfo: Displays information about the
> server</body><thread>None</thread></message>

Receiving that message xml works just fine for me.
A plugin or something may be eating the message (or it could just be
queued in the system tray - is the icon flashing?).

As a side note, you shouldn't include "<thread>None</thread>", this
indicates the start of a thread with a unique identifier of "None".
(Of course, this is not related to the message not showing up.)


More information about the Support mailing list