Subject: Interpreting errors as messages and looping?
Hi Alex,
is it possible that there is a bug in the library?
As soon as I receive XML tag like the following (which is actually an error and not a message) the OnMessage event is fired and then my bot thinks it received an actual messages and is trying to respond with another message which causes the same issue. This scenario ends up in a loop of messages.
Is it possible to detect the error somehow and not to interpret it as message?
I think this error occurs when you are using googlemail.com as domain instead of gmail.com. User 2 normally uses the e-mail address user2@gmail.com but if a customer makes a mistake and takes user2@googlemail.com as e-mail address then the issue occurs.
What do you think?
is it possible that there is a bug in the library?
As soon as I receive XML tag like the following (which is actually an error and not a message) the OnMessage event is fired and then my bot thinks it received an actual messages and is trying to respond with another message which causes the same issue. This scenario ends up in a loop of messages.
- <message xmlns="jabber:client" to="user1@gmail.com/Sharp Mess2530C034" type="error" from="user2@googlemail.com"><body>message</body><error type="modify" code="302"><gone xmlns="urn:ietf:params:xml:ns:xmpp-stanzas" /></error></message>
Is it possible to detect the error somehow and not to interpret it as message?
I think this error occurs when you are using googlemail.com as domain instead of gmail.com. User 2 normally uses the e-mail address user2@gmail.com but if a customer makes a mistake and takes user2@googlemail.com as e-mail address then the issue occurs.
What do you think?