And Joe Hildebrand spoke on 04/29/2010 03:26 PM, saying: > > On 4/29/10 4:20 PM, "Peter Saint-Andre" <stpe...@stpeter.im> wrote: > >> rfc3920bis says: >> >> If the initiating entity attempts a reasonable number of retries with >> the same SASL mechanism and all attempts fail, it MAY fall back to >> the next mechanism in its ordered list by sending a new <auth/> >> request to the receiving entity. If there are no remaining >> mechanisms in its list, the initiating entity SHOULD instead send an >> <abort/> element to the receiving entity. > > Fine. Regardless, I have to insist the the final error that's shown to the > users is some sort of bad username/password indication, rather than a socket > error. It's causing me all kinds of support issues that the error can't be > diagnosed by an end user. >
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? ~Paul [1] http://trac.adium.im/ticket/13731
signature.asc
Description: OpenPGP digital signature
