'bad request' on outgoing messages. about conversations HOT 9 CLOSED

The 'bad request' is copied straight from the servers error response. I don't have a google account to test this with...
Have you thought about switching to another xmpp provider

from conversations.

Not a bad idea, I still would prefer having as many support options as possible. Is there anything I can do to help?

from conversations.

Usually what I do when users experience problems with one particular XMPP server I ask them to provide me with a test account. In the case of gtalk this is however going to be more difficult. I could provide you with some pointers on how to debug this your self if you are willing to.

from conversations.

That'd be good. That way, even if I can't figure it out, the tips are
still here on github for others to reference.

On 14/04/14 19:37, Daniel Gultsch wrote:

Usually what I do when users experience problems with one particular
XMPP server I ask them to provide me with a test account. In the case
of gtalk this is however going to be more difficult. I could provide
you with some pointers on how to debug this your self if you are
willing to.

—
Reply to this email directly or view it on GitHub
#60 (comment).

from conversations.

This is strange. Plain text over gmail gives me a “Bad Request“ - but OTR messages are sent correctly.

from conversations.

This is strange. Plain text over gmail gives me a “Bad Request“ - but OTR messages are sent correctly.

oh thats both interesting and helpful. The difference between plain text and otr messages are that plain text messages are sent to the bare jid ([email protected]) and otr messages are sent to the full jid ([email protected]/presence)
Maybe gtalk can't handle messages sent to the bare jid (which would be really, really annoying because the xmpp standard actually encourages clients to sent messages to the bare jid)

from conversations.

This could be related to their Hangout-system in some way… All instances and the archive get the message.
Maybe you can get in other projects ideas how to solve that. (https://github.com/redsolution/xabber-android)

from conversations.

If this:

but OTR messages are sent correctly.

is true then it's most likely the barejid vs fulljid problem I have written about. Which would mean that gtalk servers don't behave like a valid xmpp server which would mean that this would be a wontfix. Conversations is an XMPP client not a gtalk client.

Maybe I'm wrong though and it's something else then we could think about fixing that.

However you should really think about switching your xmpp server. There are a lot of awesome features available if you do. carbon messages, stream managment. all this will really improve your Conversations experience.

from conversations.

I'm not sure there's enough information to say that it's bare vs full jid delivery. There might be more subtlety involved, especially since GTalk appears to work with most other XMPP clients. In particular, it works on bitlbee, which seems to happily send messages to bare jids.

I've observed this specifically when attempting to reply to chats received from friends, so presumably Conversations is sending to a full jid anyway.

from conversations.