On Mon, Nov 04, 2019 at 04:41:15PM +0300, Konstantin Khomoutov wrote:
On Sun, Nov 03, 2019 at 06:49:41PM +0100, Oswald Buddenhagen wrote:
i don't think what the server is doing is specification-conformant.
you should report it to them.
The problem is that it is highly unlikely they will do anything about
that: [...]
you should still give it a shot.
Still, regarding the flag in question — the RFC 3501 says:
| Servers MAY permit the client to define new keywords
| in the mailbox (see the description of the PERMANENTFLAGS response
| code for more information).
| A flag can be permanent or session-only on a per-flag basis.
May it be that this flag somehow gets defined as permanent by _some_
client? I have no idea - which exactly, but I do occasionally use their
web interface so, let's suppose, it's that client.
the important part is the sentence immediately before your quote -
'Keywords do not begin with "\".' ;)
the spec doesn't explicitly say that servers are forbidden from defining
their own system flags, but it's implied by "A system flag is a flag
name that is pre-defined in this specification."
yeah, it's actually calling the error() function. it probably
shouldn't, as it just continues anyway.
Should I open a bug? What is the procedure for reporting issues, anyway?
there is a bug tracker on sourceforge. but there is no need to use that
- i'm flagging the mails that require action from me. it can take a
while before i allocate another timeslice to mbsync hacking, though.
_______________________________________________
isync-devel mailing list
isync-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/isync-devel
