You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The problem also occurs in ruby 3.0.3, so I did some more digging. Bisection reveals that this is the commit that broke authenticating with PLAIN:
23f241b081d94b6385e24f550a24e65a66a0d46d is the first bad commit
commit 23f241b081d94b6385e24f550a24e65a66a0d46d
Author: nicholas a. evans <nicholas.evans@gmail.com>
Date: Tue Apr 27 16:33:27 2021 -0400
Move each authenticator to its own file
Also updates rdoc with SASL specifications and deprecations. Of these
four, only `PLAIN` isn't deprecated!
+@@authenticators+ was changed to a class instance var
+@authenticators+. No one should have been using the class variable
directly, so that should be fine.
Activity
chdiza commentedon Jan 3, 2022
The problem also occurs in ruby 3.0.3, so I did some more digging. Bisection reveals that this is the commit that broke authenticating with PLAIN:
chdiza commentedon Jan 3, 2022
Version 0.1.1 of the net-imap gem is fine. But when I install a new ruby,
gem updatebrings the buggy version of the gem into play.shugo commentedon Jan 6, 2022
@chdiza Thanks for your report. I've just released net-imap-0.2.3. Please try it.
chdiza commentedon Jan 6, 2022
Seems to work, thanks!!
nevans commentedon Jan 6, 2022
Yikes. Sorry about that. 😳 Thanks, @shugo!
Warn when using deprecated SASL mechanisms
Warn when using deprecated SASL mechanisms
Warn when using deprecated SASL mechanisms
Fix the name of CramMD5Authenticator (fixes ruby#52)