Re: client support for RFC 3516 (BINARY)?

Quoting Ken Murchison <[email protected]>:

> Hi Michael,
>
>
> On 12/05/2014 06:56 PM, Michael M Slusarz wrote:
>>
>> BINARY APPENDs are a different story though.  It is broken on  
>> multiple servers, and in several different ways.  At a minimum,  
>> versions of UW-IMAP, Cyrus, and Sun Java System Messaging have  
>> problems.
>
> I'm unaware of any issues with BINARY APPEND in Cyrus.  Have you  
> opened a bug for this?

Hi Ken,

I can't reproduce BINARY APPEND issues in current Cyrus code, at least  
with the current Debian 7 version (v2.4.16-Debian-2.4.16-4+deb7u2).  I  
believe that's why I never filed a bug since the issue now appears  
fixed.

But I can confirm that old 2.2 versions of Cyrus have this issue.   
E.g., the current Debian 6 version shows this behavior:

* OK bernard Cyrus IMAP4 v2.2.13-Debian-2.2.13-19+squeeze3 server ready
[...]
B APPEND "INBOX" (\seen) ~{200+}
B NO [UNKNOWN-CTE] Can not process the binary data

My notes additionally indicate that certain versions of Cyrus, instead  
of responding with a NO + UNKNOWN-CTE, will simply issue a BYE and  
disconnect instead.

michael


___________________________________
Michael Slusarz [[email protected]]

_______________________________________________
imapext mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/imapext