Incorrect padding: go ahead
law_ence.dev at ntlworld.com
Wed Mar 1 16:00:15 GMT 2017
On Tue, Feb 28, 2017 at 12:58:43PM +0000, ael wrote:
> On Tue, Feb 28, 2017 at 12:35:32PM +0000, ael wrote:
> > On Mon, Feb 27, 2017 at 07:22:22PM +0100, Nicolas Sebrecht wrote:
> > > On Mon, Feb 27, 2017 at 10:57:40AM +0100, Lele Gaifax wrote:
> > >
> > > > FWIW, I reported what seems the same error one year ago, with subject
> > > > "binascii.Error: Incorrect padding" (unfortunately I'm not able to reference
> > > > the thread as gmane interface isn't helping).
> > > >
> > > > In my case, the reason was that the AUTHENTICATE command resulted in a plain
> > > > string containing "go ahead".
> > > >
> > > > See also https://sourceforge.net/p/imaplib2/bugs/11/
Right. After playing more and reading bits of an rfc, it is after all the
"go ahead" violation of the IMAP protocol. So despite my last message,
Lele was absolutely right after all.
openssl s_client -connect mail.btinternet.com:993 -crlf
also seems to show other violations of rfc3501 such as in the correct
wording of some responses.
As I said earlier, I think offlineimap/imaplib2 really ought to report
the violation at the very least.
More information about the OfflineIMAP-project