In Spark do you use some custom presence status? Maybe you have set it to a negative priority? You can also try the latest build. Not sure on what OS you are using Spark, so here are two links:
Well, it must be something about AstraChat. speedy has a testing Mac OS virtual machine, maybe he can try it out and figure out what is happening. Is it happening with Pidgin-Spark combination though or Spark-Spark?
Oh, you can also enable the debugger (Login window > Advanced) and post here a sample of xml when Spark received a message from AstraChat (remove private information before posting here).
Would be great to see more xml (Received part). And mixed with messages sent from Pidgin and from AstraChat. Even more great would be to see what AstraChat sends to the server, if possible. So far i see that server thinks that Spark user is offline and adds Delay tag and a time stamp (the time is not 1:00 AM) before sending it to Spark. Not sure why it thinks that Spark is offline and then the other second it thinks that is is actually online and delivers it. Could be Openfire issue as well. What Openfire version?
Not exactly the same, but looks like an issue with Openfire 4.x and Xabber Xabber Delivering only one way chat In this case messages are delivered after client restart.
I’m going with a buggy client on this one. I can’t get it to connect to openfire (keep getting encrytion error). I even tried a few different instances…I’ve tested other clients (jitsi, pidgin, spark, etc…) with my installs and none of them had any problems. The window client connects and prompts to accept my cert, but it rebooted my machine without asking during the install processes. not happy about that! I’m staying away from this client! Now I feel like I need to change all my passwords and scan my my machine! It did not leave me with any warm and fuzzies!
Windows client is just a re-brand of Swift. I had Swift already installed and AstraChat installer said that i already have a newer version and quit Windows client works fine, no wonder. Their iOS client might be a re-brand of some good iOS open-source client, so it works fine because of that probably. Sadly, they chose to re-brand some buggy client for their Mac OS X version (or maybe it was actually their own product). I haven’t had a time to look at xml packets more closely.