https://bugs.kde.org/show_bug.cgi?id=408653
Jan Kundrát <j...@kde.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|WAITINGFORINFO |---
Ever confirmed|0 |1
Status|NEEDSINFO |CONFIRMED
--- Comment #2 from Jan Kundrát <j...@kde.org> ---
Thanks for the log (got one via private mail).
TL;DR: you won't have tags on your server, ever. Sorry, they just do not
support this feature.
Here's the relevant part:
12:27:43.8601 <<< * FLAGS (\Seen \Answered \Flagged \Deleted \Draft $MDNSent)
12:27:43.8601 <<< * OK [PERMANENTFLAGS (\Seen \Answered \Flagged \Deleted
\Draft $MDNSent)] Permanent flags
This happens during the initial mailbox sync, and the server informs us about
the set of recognized flags/keywords, and which of them can be stored
persistently. The asterisk "*" is missing, and this means that the server is
saying "I cannot save message keywords", aka tags.
This happens when we try to store a keyword:
12:27:59.5801 [task] Imap::Mailbox::UpdateFlagsTask Activated
12:27:59.6591 >>> y64 UID STORE 7 +FLAGS (broken)
12:27:59.7061 <<< * NO Keywords are not supported!
12:27:59.7061 <<< * 6 FETCH (FLAGS (\Seen))
12:27:59.7061 <<< y64 OK STORE completed.
12:27:59.7071 Warning: unhandled untagged NO...
12:27:59.7071 [task] Imap::Mailbox::UpdateFlagsTask Completed
Here, the server is telling us "you should have listened when I told you I do
no keywords!". From the specific pattern, this looks like Exchange. I stand by
my claim that it is a miserable IMAP server, but in this case I cannot really
blame the implementation because it follows the IMAP protocol spec. It's an
annoying limitation for sure, but this is a bug in Trojita for trying to
exercise an optional feature that the server told us upfront that it's not
supported.
I'll leave this bug open. Preferably, Trojita should disable tagging on
messages which are stored in a folder which doesn't support custom keywords.
This is easily detectable during the initial mailbox sync.
--
You are receiving this mail because:
You are watching all bug changes.
