[Users] [Bug 4731] New: etpan and outlook.com seems to disagree on IMAP
noreply at thewildbeast.co.uk
noreply at thewildbeast.co.uk
Mon Jan 8 21:52:41 UTC 2024
https://www.thewildbeast.co.uk/claws-mail/bugzilla/show_bug.cgi?id=4731
Bug ID: 4731
Summary: etpan and outlook.com seems to disagree on IMAP
Product: Claws Mail
Version: GIT
Hardware: PC
OS: Linux
Status: NEW
Severity: major
Priority: P3
Component: Folders/IMAP
Assignee: users at lists.claws-mail.org
Reporter: mir at datanom.net
It seems etpan and outlook.com has diverged in their interpretation on the IMAP
protocol:
** Message: 21:41:41.531: IMAP connection is un-authenticated
passwordstore.c:204:Getting password 'oauth2_access_expiry' from block (1/23)
password.c:597:Trying to decrypt password...
password.c:100:TIMING _make_key_deriv PBKDF2: 0s088ms
password.c:491:Encrypted password string length: 144
** Message: 21:41:41.619: OAuth2 access token still fresh
passwordstore.c:204:Getting password 'recv' from block (1/23)
password.c:597:Trying to decrypt password...
password.c:100:TIMING _make_key_deriv PBKDF2: 0s072ms
password.c:491:Encrypted password string length: 1168
imap-thread.c:459:found imap 0x7fded80160a0
imap-thread.c:459:found imap 0x7fded80160a0
[2024-01-08 21:41:41] IMAP> 1 CAPABILITY
[2024-01-08 21:41:41] IMAP< * CAPABILITY IMAP4 IMAP4rev1 AUTH=PLAIN
AUTH=XOAUTH2 SASL-IR UIDPLUS ID UNSELECT CHILDREN IDLE NAMESPACE LITERAL+
[2024-01-08 21:41:41] IMAP< 1 OK CAPABILITY completed.
imap-thread.c:475:generic_cb
imap-thread.c:459:found imap 0x7fded80160a0
imap-thread.c:759:capa 0
imap.c:872:got capa IMAP4
imap.c:872:got capa IMAP4rev1
imap.c:872:got capa PLAIN
imap.c:872:got capa XOAUTH2
imap.c:872:got capa SASL-IR
imap.c:872:got capa UIDPLUS
imap.c:872:got capa ID
imap.c:872:got capa UNSELECT
imap.c:872:got capa CHILDREN
imap.c:872:got capa IDLE
imap.c:872:got capa NAMESPACE
imap.c:872:got capa LITERAL+
[2024-01-08 21:41:41] IMAP> Logging XXXXX at outlook.com to outlook.office365.com
using XOAUTH2
imap-thread.c:1030:imap login - begin
imap-thread.c:459:found imap 0x2362ce0
imap-thread.c:459:found imap 0x2362ce0
[2024-01-08 21:39:56] IMAP< AUTHENTICATE completed.
imap-thread.c:1020:imap login run - end 0
imap-thread.c:475:generic_cb
imap-thread.c:459:found imap 0x2362ce0
imap-thread.c:1046:imap login - end
[2024-01-08 21:39:56] IMAP< Login to outlook.office365.com successful
imap.c:535:locking session 0x23b10b0 (0)
folder.c:4658:Folder datanom.net wants sync
folder.c:4658:Folder datanom.net wants sync
imap.c:4774:get_num_list: updating num list
imap-thread.c:867:imap list - begin
imap-thread.c:459:found imap 0x2362ce0
imap-thread.c:459:found imap 0x2362ce0
[2024-01-08 21:39:56] IMAP> 3 LIST "" ""
[2024-01-08 21:39:56] IMAP< 3 BAD User is authenticated but not connected.
imap-thread.c:857:imap list run - end
imap-thread.c:475:generic_cb
imap-thread.c:459:found imap 0x2362ce0
imap-thread.c:878:imap list - end (nil)
** (claws-mail:264775): WARNING **: 21:39:56.401: [2024-01-08 21:39:56] IMAP
error on outlook.office365.com: protocol error (very probably non-RFC
compliance from the server)
** (claws-mail:264775): WARNING **: 21:39:56.401: [2024-01-08 21:39:56] IMAP
connection broken
** (claws-mail:264775): WARNING **: 21:39:56.401: [2024-01-08 21:39:56] LIST
failed
imap-thread.c:867:imap list - begin
imap-thread.c:459:found imap 0x2362ce0
imap-thread.c:459:found imap 0x2362ce0
[2024-01-08 21:39:56] IMAP> 4 LIST "" "INBOX"
[2024-01-08 21:39:56] IMAP< 4 BAD User is authenticated but not connected.
[2024-01-08 21:39:56] IMAP< * BYE Connection closed. 14
imap-thread.c:857:imap list run - end
imap-thread.c:475:generic_cb
imap-thread.c:459:found imap 0x2362ce0
imap-thread.c:878:imap list - end (nil)
** (claws-mail:264775): WARNING **: 21:39:56.431: [2024-01-08 21:39:56] IMAP
error on outlook.office365.com: protocol error (very probably non-RFC
compliance from the server)
** (claws-mail:264775): WARNING **: 21:39:56.431: [2024-01-08 21:39:56] IMAP
connection broken
** (claws-mail:264775): WARNING **: 21:39:56.431: [2024-01-08 21:39:56] LIST
failed
--
You are receiving this mail because:
You are the assignee for the bug.
More information about the Users
mailing list