Re: client support for RFC 3516 (BINARY)?

Thanks for the responses. A couple of follow-up questions:

1. This thread (
http://mailman13.u.washington.edu/pipermail/imap-protocol/2012-August/001803.html)
implies that fetching non-terminal MIME parts, while allowed by the spec,
is strongly discouraged because it may require rewriting CTE headers and
other on-the-fly modifications. Are people typically restricting the use of
BINARY to terminal parts, or are they issuing things like FETCH BINARY[] ?

2. Some folks indicated they use BINARY append. Does mean you're also using
a binary CTE in your messages, or that you're just using literal8 syntax to
upload messages that are 7bit or 8bit?

On Fri, Dec 5, 2014 at 2:02 PM, Jamie Nicolson (倪志明) <[email protected]>
wrote:

> Anyone know of clients that support RFC 3516? It seems like it could be
> particularly useful for mobile clients, to reduce both download size and
> CPU usage for base64-decoding.
>

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