ejabberd - Comments for "Message packet rejected if to attribute contains Resource"

clarification

BCaseyHanks — Thu, 04 Dec 2008 13:52:23 +0000

Thanks for the comment.

The original samples I posted did have the "/" the wrong way.
This mistake does not occur in my code and occured only becuase I mistyped the sample during my post.
If you look at the clarrify samples (where I copied and pasted the XML directly) you will notice that the JID is formatted correctly.

so I am still at a loss as to the source of the problem.

Casey

All works correctly for me!

mfoss — Thu, 04 Dec 2008 11:57:51 +0000

I use ejabberd trunk SVN, and two Tkabber 0.12.0 clients. All works correctly here.

BCaseyHanks wrote:

The following message is not being delivered by the server:

<message id="JN_26" from="chanks@v-doc-imchat.infoassure.local" to="btroxell@v-doc-imchat.infoassure.local"><x jid="room1@conference.v-doc-imchat.infoassure.local" xmlns="jabber:x:conference" /></message>

chanks sends:

<message id="JN_26" from="chanks@v-doc-imchat.infoassure.local" 
to="btroxell@v-doc-imchat.infoassure.local">
<x jid="room1@conference.v-doc-imchat.infoassure.local" xmlns="jabber:x:conference" />
</message>

btroxell receives:

<message from='chanks@v-doc-imchat.infoassure.local/N2K'
	id='JN_26'
	xml:lang='es'
	to='btroxell@v-doc-imchat.infoassure.local'>
  <x xmlns='jabber:x:conference'
	jid='room1@conference.v-doc-imchat.infoassure.local'/>
</message>

BCaseyHanks wrote:

The following message is also not being delivered:

<message id="JN_27" to="btroxell@v-doc-imchat.infoassure.local" type="chat" from="chanks@v-doc-imchat.infoassure.local/N2K"><thread>5a72cf4a-cd21-46fa-bc0f-b0ea927bae73</thread><body>ping</body></message>

chanks sends:

<message id="JN_27" to="btroxell@v-doc-imchat.infoassure.local" type="chat" 
from="chanks@v-doc-imchat.infoassure.local/N2K">
<thread>5a72cf4a-cd21-46fa-bc0f-b0ea927bae73</thread><body>ping</body></message>

btroxell receives:

<message from='chanks@v-doc-imchat.infoassure.local/N2K'
	id='JN_27'
	xml:lang='es'
	type='chat'
	to='btroxell@v-doc-imchat.infoassure.local'>
  <thread>5a72cf4a-cd21-46fa-bc0f-b0ea927bae73</thread>
  <body>ping</body>
</message>

BCaseyHanks wrote:

The following message IS being delivered:

<message id="JN_17" to="chanks@v-doc-imchat.infoassure.local/N2K" type="chat" from="btroxell@v-doc-imchat.infoassure.local/N2K"><thread>4b758a5d-b2ee-492a-9480-0e8d53aea307</thread><body>ping</body></message>

chanks sends:

<message id="JN_17" to="chanks@v-doc-imchat.infoassure.local/N2K" type="chat" 
from="btroxell@v-doc-imchat.infoassure.local/N2K">
<thread>4b758a5d-b2ee-492a-9480-0e8d53aea307</thread><body>ping</body></message>

chanks receives:

<message from='chanks@v-doc-imchat.infoassure.local/N2K'
	id='JN_17'
	xml:lang='es'
	type='chat'
	to='chanks@v-doc-imchat.infoassure.local/N2K'>
  <thread>4b758a5d-b2ee-492a-9480-0e8d53aea307</thread>
  <body>ping</body>
</message>

BCaseyHanks wrote:

The following message result in an error:

<message id="JN_24" from="btroxell@v-doc-imchat.infoassure.local" to="chanks@v-doc-imchat.infoassure.local\n2k"><x jid="room1@conference.v-doc-imchat.infoassure.local" xmlns="jabber:x:conference" /></message>

That stanza has the To JID wrongly formed, as I explained before.

user@server/resource

mfoss — Thu, 04 Dec 2008 11:36:24 +0000

You made here a very simple mistake :)

BCaseyHanks wrote:

<message id="JN_23" from="source@server\custom" to="destination@server\spark"><x jid="room1@server" xmlns="jabber:x:conference" /></message>

In that XMPP stanza, the destination JID is user "destination" and server "server\spark". The separator for resource is /, not \. So you didn't build your destination JID correctly.

XMPP-Core: Addressing Scheme

jid             = [ node "@" ] domain [ "/" resource ]

The sender JID is of course also wrong: "source@server\custom". However, ejabberd did not complain to you because ejabberd just throws the attribute "FROM" to the trash to avoid malicious users to fake their identity. I found this behaviour in XMPP-IM-bis: 9.1.2.1. Client-to-Server Streams:

Quote:

2. When the server receives an XML stanza from a client and the stanza includes a 'from' attribute, the server MUST either (a) [...] or (b) override the provided 'from' attribute by adding a 'from' attribute as specified under Rule #1.

clarification

BCaseyHanks — Wed, 03 Dec 2008 20:51:43 +0000

Suppose the following two clients are logged on:
1) IM custom (logged in as chanks@v-doc-imchat.infoassure.local\N2K)
2) IM custom (logged in as btroxell@v-doc-imchat.infoassure.local\N2K)

The following message is not being delivered by the server:

<message id="JN_26" from="chanks@v-doc-imchat.infoassure.local" to="btroxell@v-doc-imchat.infoassure.local"><x jid="room1@conference.v-doc-imchat.infoassure.local" xmlns="jabber:x:conference" /></message>

The following message is also not being delivered:

<message id="JN_27" to="btroxell@v-doc-imchat.infoassure.local" type="chat" from="chanks@v-doc-imchat.infoassure.local/N2K"><thread>5a72cf4a-cd21-46fa-bc0f-b0ea927bae73</thread><body>ping</body></message>

The following message IS being delivered:

<message id="JN_17" to="chanks@v-doc-imchat.infoassure.local/N2K" type="chat" from="btroxell@v-doc-imchat.infoassure.local/N2K"><thread>4b758a5d-b2ee-492a-9480-0e8d53aea307</thread><body>ping</body></message>

The following message result in an error:

<message id="JN_24" from="btroxell@v-doc-imchat.infoassure.local" to="chanks@v-doc-imchat.infoassure.local\n2k"><x jid="room1@conference.v-doc-imchat.infoassure.local" xmlns="jabber:x:conference" /></message>

Message that comes back with error:

<message from='chanks@v-doc-imchat.infoassure.local\n2k' to='btroxell@v-doc-imchat.infoassure.local/N2K' type='error' id='JN_24'><x jid='room1@conference.v-doc-imchat.infoassure.local' xmlns='jabber:x:conference'/><error code='404' type='cancel'><remote-server-not-found xmlns='urn:ietf:params:xml:ns:xmpp-stanzas'/></error></message>

Thus for my client

Message packets without an x element are only delivered if the 'to' incluces the Resource
Message packets with an x element generate an error if the 'to' includes the Resource
Message packets with an x element seem to do nothing if the 'to' is a Bare JID

Thanks,

Casey