v2.2.28 release candidate released

[Timo Sirainen]

On 20 Feb 2017, at 14.06, A.L.E.C <alec at alec.pl> wrote:
> 
> In RFC3501 [PARSE] is described as "The human-readable text represents
> an error in parsing the [RFC-2822] header or [MIME-IMB] headers of a
> message in the mailbox.". So, is this really an appropriate error code
> for this case?

I think it's the closest to being correct. It's saying that there was some kind of a parsing problem with the email. RFC 3501 only talks about headers, but that's probably because they hadn't really considered parsing errors in email bodies.

The IMAP BINARY RFC only talks about [UNKNOWN-CTE], but it says it should be sent on unknown Content-Transfer-Encoding. So reusing it for other purposes seems more wrong than using [PARSE].

This was discussed some years ago in imap mailing list:
http://mailman13.u.washington.edu/pipermail/imap-protocol/2012-December/001914.html <http://mailman13.u.washington.edu/pipermail/imap-protocol/2012-December/001914.html>
http://mailman13.u.washington.edu/pipermail/imap-protocol/2012-December/001925.html <http://mailman13.u.washington.edu/pipermail/imap-protocol/2012-December/001925.html>