The from JID needs to be fully qualified, i.e MUST have a resource.
<message to="ridder.ben at gmail.com" from="ben at siemens.be/some-resource"
type="chat"><body>test</body></message>
Jean-Louis
-----Original Message-----
Message: 1
Date: Mon, 30 Jan 2006 11:03:19 +0100
From: Ben Turner <ext.ben.turner at siemens.be>
Subject: [jdev] googletalk
To: jdev at jabber.org
Message-ID: <20060130100319.GA1874 at bturner>
Content-Type: text/plain; charset=us-ascii
Hi,
I am sending the following message to a googletalk recipient over S2S:
<message to="ridder.ben at gmail.com" from="ben at siemens.be"
type="chat"><body>test</body></message>
However i am getting the following error:
<message to="ben at siemens.be" from="ridder.ben at gmail.com"
type="error"><body>test</body><error code="400" type="modify"><bad-request
xmlns="urn:ietf:params:xml:ns:xmpp-stanzas"/></error></message>
I know google does an amount of strict checking, however i cannot figure out
what is wrong with the above message.
Any ideas?
Thanks,
Ben
--
Ben Turner
SIEMENS - COM D MN B
tel: +32 14 252326
~ Scientia Vincere Tenebras ~
------------------------------
Message: 2
Date: Mon, 30 Jan 2006 11:10:27 +0100
From: Remko Troncon <remko at el-tramo.be>
Subject: [jdev] Re: googletalk
To: Jabber software development list <jdev at jabber.org>
Message-ID: <20060130101027.GD5245 at iris.cs.kuleuven.be>
Content-Type: text/plain; charset=us-ascii
> I am sending the following message to a googletalk recipient over S2S:
Is the recipient on your contact list, and vice versa ?
cheers,
Remko
------------------------------
Message: 3
Date: Mon, 30 Jan 2006 12:19:22 +0200
From: Norman Rasmussen <norman at rasmussen.co.za>
Subject: Re: [jdev] googletalk
To: Jabber software development list <jdev at jabber.org>
Message-ID:
<5b698f5a0601300219v15758612pe3a0d38739993e32 at mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Have you added 'ben at siemens.be' as a contact on
'ridder.ben at gmail.com's contact list. If you don't then gtalk doesn't
let the message through.
Also what's your stream default namespace? If it's not jabber:server
(or jabber:client after they relaxed the validation), then the entire
connection is dropped.
On 1/30/06, Ben Turner <ext.ben.turner at siemens.be> wrote:
>
> Hi,
>
> I am sending the following message to a googletalk recipient over S2S:
>
> <message to="ridder.ben at gmail.com" from="ben at siemens.be"
type="chat"><body>test</body></message>
>
> However i am getting the following error:
>
> <message to="ben at siemens.be" from="ridder.ben at gmail.com"
type="error"><body>test</body><error code="400" type="modify"><bad-request
xmlns="urn:ietf:params:xml:ns:xmpp-stanzas"/></error></message>
>
> I know google does an amount of strict checking, however i cannot figure
out
> what is wrong with the above message.
>
> Any ideas?
>
> Thanks,
>
> Ben
>
> --
> Ben Turner
> SIEMENS - COM D MN B
> tel: +32 14 252326
>
> ~ Scientia Vincere Tenebras ~
>
>
--
- Norman Rasmussen
- Email: norman at rasmussen.co.za
- Home page: http://norman.rasmussen.co.za/
------------------------------
Message: 4
Date: Mon, 30 Jan 2006 11:29:24 +0100
From: Ben Turner <ext.ben.turner at siemens.be>
Subject: Re: [jdev] Re: googletalk
To: Jabber software development list <jdev at jabber.org>
Message-ID: <20060130102924.GB1874 at bturner>
Content-Type: text/plain; charset=us-ascii
On Mon, Jan 30, 2006 at 11:10:27AM +0100, Remko Troncon wrote:
> Is the recipient on your contact list, and vice versa ?
Does googletalk require that the sender of messages is on the recipients
roster?
thanks,
B
--
Ben Turner
SIEMENS - COM D MN B
tel: +32 14 252326
~ Scientia Vincere Tenebras ~
------------------------------
Message: 5
Date: Mon, 30 Jan 2006 11:36:54 +0100
From: Remko Troncon <remko at el-tramo.be>
Subject: [jdev] Re: Re: googletalk
To: Jabber software development list <jdev at jabber.org>
Message-ID: <20060130103654.GA10434 at iris.cs.kuleuven.be>
Content-Type: text/plain; charset=us-ascii
> Does googletalk require that the sender of messages is on the recipients
roster?
In a word: yes.
cheers,
Remko
------------------------------
Message: 6
Date: Tue, 31 Jan 2006 00:12:11 +1100
From: Trejkaz <trejkaz at trypticon.org>
Subject: Re: [jdev] Re: googletalk
To: Jabber software development list <jdev at jabber.org>
Message-ID: <200601310012.13665.trejkaz at trypticon.org>
Content-Type: text/plain; charset="iso-8859-1"
On Monday 30 January 2006 21:10, Remko Troncon wrote:
> > I am sending the following message to a googletalk recipient over S2S:
>
> Is the recipient on your contact list, and vice versa ?
Wouldn't that have been the wrong error code if that's the case? It wasn't
a
bad request...
TX
--
Email: trejkaz at trypticon.org
Jabber ID: trejkaz at trypticon.org
Web site: http://trypticon.org/
GPG Fingerprint: 9EEB 97D7 8F7B 7977 F39F A62C B8C7 BC8B 037E EA73
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url :
https://www.jabber.org/jdev/attachments/20060131/a36e5500/attachme
nt-0001.pgp
------------------------------
Message: 7
Date: Mon, 30 Jan 2006 15:01:37 +0100
From: Ralph Meijer <jabber.org at ralphm.ik.nu>
Subject: Re: [jdev] Re: googletalk
To: Jabber software development list <jdev at jabber.org>
Message-ID: <20060130140137.GA4051 at ik.nu>
Content-Type: text/plain; charset=us-ascii
On Tue, Jan 31, 2006 at 12:12:11AM +1100, Trejkaz wrote:
> On Monday 30 January 2006 21:10, Remko Troncon wrote:
> > > I am sending the following message to a googletalk recipient over S2S:
> >
> > Is the recipient on your contact list, and vice versa ?
>
> Wouldn't that have been the wrong error code if that's the case? It
wasn't a
> bad request...
Well, yes indeed. I regard this policy as a set of hardwired privacy
rules per RFC 3921 (XMPP IM), section 10, and more specifically
instances of the examples on blocking messages in section 10.9. The
rules for blocked communication attempts are described in section 10.14:
If a blocked entity attempts to send message or presence stanzas to
the user, the user's server SHOULD silently drop the stanza and MUST
NOT return an error to the sending entity.
If a blocked entity attempts to send an IQ stanza of type "get" or
"set" to the user, the user's server MUST return to the sending entity
a <service-unavailable/> stanza error, since this is the standard
error code sent from a client that does not understand the namespace
of an IQ get or set. IQ stanzas of other types SHOULD be silently
dropped by the server.
--
Groetjes,
ralphm
------------------------------
Message: 8
Date: Mon, 30 Jan 2006 09:27:52 -0700
From: Peter Saint-Andre <stpeter at jabber.org>
Subject: Re: [jdev] Idea repository?
To: Jabber software development list <jdev at jabber.org>
Message-ID: <43DE3E88.7050105 at jabber.org>
Content-Type: text/plain; charset="iso-8859-1"
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Adam Hunt wrote:
> As I'm sure everyone is aware Jabber/XMPP has an unbelievably large number
> of potential applications. I feel that a repository of ideas is
warranted.
> It would be a place where people could post ideas for application that
they
> don't have the time or skill to develop further.
We have a wiki here:
http://wiki.jabber.org/
Ping one of the Sysops if you need an account:
http://wiki.jabber.org/index.php/Sysops
Peter
- --
Peter Saint-Andre
Jabber Software Foundation
http://www.jabber.org/people/stpeter.shtml
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFD3j6INF1RSzyt3NURAreCAKCEvw9Iy71aj4T8oVwNkNLtoOIYcwCePyQY
zrNPVQB0GQ4A65sSWulm+xo=
=qID/
-----END PGP SIGNATURE-----
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 3641 bytes
Desc: S/MIME Cryptographic Signature
Url :
https://www.jabber.org/jdev/attachments/20060130/2a59d7a9/smime-00
01.bin
------------------------------
_______________________________________________
jdev mailing list
jdev at jabber.org
http://mail.jabber.org/mailman/listinfo/jdev
End of jdev Digest, Vol 24, Issue 38
************************************