https://bugs.kde.org/show_bug.cgi?id=381461
Bug ID: 381461
Summary: hard lockup after ParseError
Product: trojita
Version: git
Platform: Other
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: IMAP
Assignee: trojita-b...@kde.org
Reporter: kdeb...@equaeghe.nospammail.net
Target Milestone: ---
Created attachment 106201
--> https://bugs.kde.org/attachment.cgi?id=106201&action=edit
screenshot of error message
After restoring a message from backup in the web interface of my mail provider,
FastMail, Trojita chokes on (I strongly suspect) that message. To wit, I get a
ParseError: getPossiblyBackslashedAtom: did not read anything
with clarification:
* 22 FETCH (FLAGS (\Seen $X-ME-Annot-2 werk [EXPUNGED]) UID 2006 MODSEQ
(673451))
^ here
Somebody else already established from the RFC that ] is not allowed there
<http://www.lumisoft.ee/Forum/yaf_postsm24658_Invalid-IMAP-flags.aspx#post24658>
and I guess this is baked into Trojita:
flag-keyword = atom
ATOM-CHAR = <any CHAR except atom-specials>
atom-specials = "(" / ")" / "{" / SP / CTL / list-wildcards /
quoted-specials / resp-specials
resp-specials = "]"
So this seems to be a clear server-side issue. I will contact my mail provider.
I'll see if I can find a more lenient client that will allow me to clear the
offending keyword.
I don't know whether Trojita is supposed to be able to deal with this, but
after retriggering the issue by re-opening the mailbox with the offending
message a couple of times, Trojita locks up the window manager hard. Namely, I
need to go to a console (Ctrl-Alt-F2) and sigterm Trojita from there to get the
window manager back responding. I do think that is not supposed to happen.
--
You are receiving this mail because:
You are watching all bug changes.
