Your message dated Mon, 8 Jul 2024 21:41:47 +0100 with message-id <ZoxPCyvAz1iMaQSK@shelf.conquest> and subject line Problem no longer exists. has caused the Debian Bug report #997933, regarding offlineimap3: 'int' object is not subscriptable when connecting to outlook.office365.com to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 997933: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997933 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Package: offlineimap3 Version: 0.0~git20211018.e64c254+dfsg-1 Severity: serious Justification: 4 In the last week or so, offlineimap is usually (but not always) failing to connect to outlook.office365.com reporting: $ offlineimap -a xxxxx OfflineIMAP 8.0.0 Licensed under the GNU GPL v2 or any later version (with an OpenSSL exception) imaplib2 v3.05, Python v3.9.7, OpenSSL 1.1.1l 24 Aug 2021 Account sync xxxxx: *** Processing account xxxxx Establishing connection to outlook.office365.com:993 (oRemote) ERROR: While attempting to sync account 'xxxxx' 'int' object is not subscriptable *** Finished account 'xxxxx' in 0:00 ERROR: Exceptions occurred during the run! ERROR: While attempting to sync account 'xxxxx' 'int' object is not subscriptable 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 683, in acquireconnection e.args[0][:35] == 'IMAP4 protocol error: socket error:': ----------------------------------------------------------------- I suspect perhaps a change in some python package? When this first showed up, it was nondeterministic: it looked like some sort of time out of, presumably some state somewhere. But now it seems to be pretty solid. Of course, MS maybe have messed up their IMAP server. -- System Information: Debian Release: bookworm/sid APT prefers testing-debug APT policy: (500, 'testing-debug'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.14.0-2-amd64 (SMP w/8 CPU threads) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB:en Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages offlineimap3 depends on: ii ca-certificates 20210119 ii python3 3.9.2-3 ii python3-distro 1.6.0-2 ii python3-imaplib2 2.57-5.2 offlineimap3 recommends no packages. Versions of packages offlineimap3 suggests: pn python3-gssapi <none> -- no debconf information Here is the relevant part of offlineimap.rc: --------------------------------------------------- [general] accounts = one,two,three,... #fsync false to conserve flash write cycles fsync = false [Account xxxxx] localrepository = sLocal remoterepository = sRemote [Repository sRemote] type = IMAP ssl = yes ssl_version = tls1 sslcacertfile = /etc/ssl/certs/ca-certificates.crt remoteprt = 993 remotehost = outlook.office365.com remoteuser = xxxxxxxxxx@somewhere.something folderfilter = lambda foldername: foldername in ['INBOX', 'Junk Email', 'Sent Items'] [Repository sLocal] type = Maildir localfolders = ~/Mail/xxxxx sep = / # Next again to help flash conservation & because noatime set restoreatime = yes -------------------------------------------------------------------------
--- End Message ---
--- Begin Message ---This problem no longer happens, so I am closing this bug.
--- End Message ---
