When trying to get pop mail with mutt (1.4.2.2-3), sasl authentication will always fail. This is due to a change in cyrus-sasl version 2.1.22, as described in mutt bug 2478. (Open URL, log in with user:guest pass:guest to see it.) The patch the mutt devs have applied to fix this is here (CVS HEAD): http://dev.mutt.org/cgi-bin/viewcvs.cgi/mutt/pop_auth.c?r1=3.7&r2=3.8 This patch to pop_auth.c is hard to backport however, because of another patch in the mutt src rpm: mutt-1.4-sasl2.patch. But the part that matters is: -sasl_decode64 (inbuf, strlen (inbuf), buf, LONG_STRING-1, &len) != SASL_OK) +sasl_decode64 (inbuf+2, strlen (inbuf+2), buf, LONG_STRING-1, &len) != SASL_OK) I removed the leading spaces and && here to fit it on one line. I think the other changes in their fix are to "enable SASL plaintext: $foo_authenticators [as] a more general solution" as their cvs log says. Since the equivalent line in 1.4 is also altered by the sasl2 patch I'm not sure how to propose a patch, in fact I tested this fix by editing the sasl2 patch. Anyway, add '+2' to both 'inbuf's in that line and sasl auth will work again.
Fixed in mutt-1.4.2.2-4.fc6. Thanks.
mutt-1.4.2.2-4.fc6 has been pushed for fc6, which should resolve this issue. If these problems are still present in this version, then please make note of it in this bug report.
List of patches present on mutt-1.5.20-6.20091214hg736b6a.el6: http://pkgs.devel.redhat.com/cgit/rpms/mutt/commit/?h=rhel-6.6&id=5e5acce3e9664eb459e94bbacfedb071d51bb888
Recovering unwanted changes caused by a badly chosen bug number choice.