Package: offlineimap3
Version: 0.0~git20211018.e64c254+dfsg-2
Severity: normal

Trying to connect to outlook.office365.com:993 today I am getting the 
quite well known 
"'User is authenticated but not connected.'" LIST command error

I have checked that my refresh token in .offlineimaprc file is up to
date, although the error saying that I am authenticated really excluded
that. offlineimap3 is working normally with other imap servers. It is
just the OAUTH connection to the micros$$$ server which seems to be
broken.

I should add that I am using the shortcut oauth2_client_id for thunderbird.
I suppose that just might be relevant.

Here is the dialogue, but it doesn't help much:
-------------------------------------------------------------
offlineimap -a somewhere
OfflineIMAP 8.0.0
  Licensed under the GNU GPL v2 or any later version (with an OpenSSL exception)
imaplib2 v3.05, Python v3.11.4, OpenSSL 3.0.9 30 May 2023
Account sync somewhere:
 *** Processing account somewhere
 Establishing connection to outlook.office365.com:993 (somewhereRemote)
 ERROR: While attempting to sync account 'somewhere'
  LIST command error: BAD [b'User is authenticated but not connected.']. Data: 
b'BENK7 LIST "" ""\r\n'
 *** Finished account 'somewhere' in 0:00
ERROR: Exceptions occurred during the run!
ERROR: While attempting to sync account 'somewhere'
  LIST command error: BAD [b'User is authenticated but not connected.']. Data: 
b'BENK7 LIST "" ""\r\n'

Traceback:
  File "/usr/share/offlineimap3/offlineimap/accounts.py", line 298, in 
syncrunner
    self.__sync()
  File "/usr/share/offlineimap3/offlineimap/accounts.py", line 374, in __sync
    remoterepos.getfolders()
  File "/usr/share/offlineimap3/offlineimap/repository/IMAP.py", line 681, in 
getfolders
    imapobj = self.imapserver.acquireconnection()
              ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/share/offlineimap3/offlineimap/imapserver.py", line 612, in 
acquireconnection
    listres = imapobj.list(self.reference, '""')[1]
              ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3/dist-packages/imaplib2.py", line 896, in list
    return self._simple_command(name, directory, pattern, **kw)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3/dist-packages/imaplib2.py", line 1684, in 
_simple_command
    return self._command_complete(self._command(name, *args), kw)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3/dist-packages/imaplib2.py", line 1431, in 
_command_complete
    raise self.error('%s command error: %s %s. Data: %.100s' % (rqb.name, typ, 
dat, rqb.data))

--------------------------------------------------------------------------------

I have checked the upstream github for any recent changes that might be
relevant, but found nothing obvious. I looked through the traceback path
in the sources, but could see nothing helpful.

offlineimap3 was working on this connection yesterday. It failed after
my routine "apt (dist)upgrade" this morning, but that is probably a
coincidence. Perhaps MS have changed something? Searching suggests that
their Imap server is buggy as usual with MS...

If this error persists, it may need investigating...

As below, I don't have python3-gssapi installed in case that is
relevant.

------------------------------------------------------------------------

-- System Information:
Debian Release: trixie/sid
  APT prefers testing-debug
  APT policy: (500, 'testing-debug'), (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.3.0-1-amd64 (SMP w/8 CPU threads; PREEMPT)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_GB:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages offlineimap3 depends on:
ii  ca-certificates   20230311
ii  python3           3.11.2-1+b1
ii  python3-distro    1.8.0-1
ii  python3-imaplib2  2.57-5.2

offlineimap3 recommends no packages.

Versions of packages offlineimap3 suggests:
pn  python3-gssapi  <none>

-- no debconf information

Reply via email to