No, and thank you for asking.
Priority is getting IMAP working and fully implemented for all clients (except outlook...) It would be beneficial to support the IMAPx, for the server to be able to push email to clients by supporting IDLE, but if that is too difficult to start with, then just fixing the broken implementation of IMAP4rev1 would be a good start. The current support for IMAP works, but not on all clients, and not all features. These are my observations so far regarding IMAP - * FETCH command is split in the middle of the command (according to RFC822, headers can be split by newline, but not the command itself) > per https://tools.ietf.org/html/rfc3501 > >9. Formal Syntax > The following syntax specification uses the Augmented Backus-Naur > Form (ABNF) notation as specified in [ABNF]. In the case of >alternative or optional rules in which a later rule overlaps an earlier >rule, the rule which is listed earlier MUST take priority. For example, >"\Seen" when parsed as a flag is the \Seen flag name and not a >flag-extension, even though "\Seen" can be parsed as a flag-extension. >Some, but not all, instances of this rule are noted below. >Note: [ABNF] rules MUST be followed strictly; in particular: > (1) Except as noted otherwise, all alphabetic characters are >case-insensitive. The use of upper or lower case characters to >define token strings is for editorial clarity only. Implementations >MUST accept these strings in a case-insensitive fashion. >(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. (3) The ASCII NUL character, >%x00, MUST NOT be used at any time. fetch = "FETCH" >SP sequence-set SP ("ALL" / "FULL" / "FAST" / fetch-att / "(" fetch-att *(SP >fetch-att) ")") fetch-att = "ENVELOPE" / "FLAGS" / "INTERNALDATE" / >"RFC822" [".HEADER" / ".SIZE" / ".TEXT"] / "BODY" ["STRUCTURE"] / "UID" / >"BODY" section ["<" number "." nz-number ">"] / "BODY.PEEK" section ["<" >number "." nz-number ">"] The output from citadel as of current (an example logged from evolution) > [imapx:A] I/O: '* 1 FETCH (UID 145342 RFC822.SIZE 3918 ^M > > RFC822.HEADER {247}^M > > Return-Path: [email protected]^M > > Date: Sun, 29 Jan 2017 11:35:31 -0500^M > > To: [email protected]^M > > Subject: Test^M > > Message-ID: <[email protected]>^M > > From: "User B" <[email protected]>^M > > FLAGS (\Seen))^M > > > > with an explanation from the devs there... https://bugzilla.gnome.org/show_bug.cgi?id=780617 * IMAP flags / tags being cleared (client supplied, like labels, important flags, etc) I am not so much asking for the web client to implement them, but if the server could not strip the tags which the client adds... We can start there, and re-evaluate after that. Let me know if that is not clear enough :) Thank you for all that you do. > Tue Apr 04 2017 09:19:19 PM EDT from IGnatius T Foobar @ Uncensored >Subject: Re: Status? > > >Ok, for starters I have to apologize for appearing to have gone missing for >a little while in terms of development. I had a little thing I wanted to do >with citserver and ended up going down a rabbit hole that was way deeper than >I planned. > >So ... is the address book on room access controls still our top priority? > > > >
