On 4/29/10 6:07 PM, "Paul Aurich" <p...@darkrain42.org> wrote:
> I'd be interested in knowing if this still occurs with a more recent build > (it sounds like the same underlying issue as the dueling banjo^Wresources > issue you reported a few months ago [1], but I don't think there's been a > beta since then). If it still occurs with that patch, do you have a debug > log / XML stream? At what point does the server forcibly kill off the TCP > session? See the attached log, from 1.4b17. You can see that the target server supports two SASL mechanisms, including one proprietary one, and does not support XEP-78. It's the XEP-78 iq that kills the connection. -- Joe Hildebrand
error.log
Description: Binary data
