In version 0.7 for windows, I get the following error: ParseError: getAtom: did not read anything * STATUS "INBOX" (MESSAGES 702 UNSEEN 0 RECENT 0) ^ here Probably because there are two spaces between * and STATUS? It connects to a DevMail Gateway that works for thunderbird. Reproducible: Always
According to RFC 3501, Section 9 (https://tools.ietf.org/html/rfc3501#section-9) only one space is allowed between the * and the STATUS keyword: "(2) In all cases, SP refers to exactly one space. It is NOT permitted to substitute TAB, insert additional spaces, or otherwise treat SP as being equivalent to LWSP." "response-data = "*" SP (resp-cond-state / resp-cond-bye / mailbox-data / message-data / capability-data) CRLF" and "mailbox-data = "FLAGS" SP flag-list / "LIST" SP mailbox-list / "LSUB" SP mailbox-list / "SEARCH" *(SP nz-number) / "STATUS" SP mailbox SP "(" [status-att-list] ")" / number SP "EXISTS" / number SP "RECENT""
> only one space is allowed between the * and the STATUS keyword: Oh yeah, that server is clearly broken, but we've added similar compatibility quirks before. Jaime, could you please confirm that reinstalling Trojita using [1] fixes this issue for you? [1] http://ci-logs.kde.flaska.net/binaries/trojita/win32/check/Trojita-Setup-767-12d9c5a750814e64b4e2483ae862f633.exe
Yes, with that setup trojitá works with this server. In any case, I'll inform that server developers about that issue. Best regards.
Let's reopen this bug until that patch actually hits some branch in our git repo; right now, it's under review. Feedback is welcome at https://gerrit.vesnicky.cesnet.cz/r/767 .
Git commit 6c17000002437b67c690d892be0dc014b2ef0db3 by Jan Kundrát. Committed on 07/07/2016 at 14:59. Pushed by gerrit into branch 'master'. IMAP: Accept more spaces when reading untagged responses The IMAP standard is 100% clear on this one, but apparently there are servers out there which get this thing wrong and send extra spaces every now and then -- a "DevMail Gateway" is one of these, according to the linked bug. That behavior is incorrect and in violation of RFC3501, but whatever, we've added similar incompatibility quirks before and I'm afraid that we'll have to keep adding them in future, too. Let's see if this is enough to work with the above mentioned server implementation. Change-Id: Iff89b82ca3ca4be719076e3ee81176b8fc7d287c M +1 -0 src/Imap/Parser/Parser.cpp M +7 -0 tests/Imap/test_Imap_Parser_parse.cpp http://commits.kde.org/trojita/6c17000002437b67c690d892be0dc014b2ef0db3