#345

reported by @ilbelkyr

I just accidentally reproduced the SASL failure on autoreconnect issue, and again, doing /rmreconns and connecting manually fixed it. I managed to grab rawlog, and apparently it's sending different things in the AUTHENTICATE message; I'll see if I can share them without revealing passwords

fwiw, what it's sending in the failure case is valid base64; but instead of ilbelkyr\0ilbelkyr\0password, it puts ilbelkyr (my username) as the password, and some random base64-looking data (which doesn't appear to decode to anything meaningful) as the username