I built some test tools using code snippets I found on this site for xmpppy. And I'm using the tools against Openfire XMPP server (on Windows). What's interesting is that the code samples here use port 5223, which is to enable TLS/SSL where available.
My tools work fine under that. But we recently made a change to Openfire to not use TLS and SSL because of some issues we have and my tools didn't work using port 5223. So I worked around it with various tweaks changing back to use default of port 5222.
But what I find puzzling is that with non TLS/SSL connections over port 5222 to Openfire, my tools connect OK and send initial presence OK, but then fail to do what they were designed to do (e.g. echo back messages it receives or send out messages to other users like a bot). It just does nothing after connecting and sending initial presence, or it does it once or a few times and then stops doing it.
Anyone have any thoughts to this behavior? Is this an issue with xmpppy? Or how I've configured it in the code? Or an issue with Openfire?
I have one tool built using Jabber.NET that changes presence and that seems to work OK. Need to check sending messages with Jabber.NET to compare.
Here's some of the various changes I made to have it connect successfully, but with same outcome:
cnx.connect(server=(svr,5222),proxy=None,secure=0)
cnx.connect()
cnx.connect(server=(svr,5222))
where it simply used to be
cnx.connect(server=(svr,5223))