diff options
| author | Guilhem Moulin <guilhem@fripost.org> | 2015-09-15 16:48:29 +0200 |
|---|---|---|
| committer | Guilhem Moulin <guilhem@fripost.org> | 2015-09-15 17:10:11 +0200 |
| commit | 90d926f6f32dd3ff06e5c49e6a982777ead9f691 (patch) | |
| tree | 0d91c1c134a439344737a34f99fe90036f6e03f6 /README | |
| parent | 6011b94a5c6f0b787ce883b5646684828a54a994 (diff) | |
Remove support for the Binary Content extension [RFC3516].
“If the server does not know how to decode the section's CTE, it MUST
fail the request and issue a "NO" response that contains the
"UNKNOWN-CTE" extended response code.” — [RFC3516 section 4.3]
Unfortunately the client doesn't know which message couldn't be decoded,
so it can't fallback and use BODY instead.
This made ‘use-binary=NO’ pretty much mandatory. Hence we remove
support for BINARY [RFC3516]. Instead, we increase the thresold for
when to add Zlib full flush points from 4096 to the buffer size (32768).
Diffstat (limited to 'README')
| -rw-r--r-- | README | 5 |
1 files changed, 2 insertions, 3 deletions
@@ -28,9 +28,8 @@ extensions are: * LITERAL+ [RFC2088] non-synchronizing literals (recommended), * MULTIAPPEND [RFC3502] (recommended), * COMPRESS=DEFLATE [RFC4978] (recommended), - * SASL-IR [RFC4959] SASL Initial Client Response, - * UNSELECT [RFC3691], and - * BINARY [RFC3516]. + * SASL-IR [RFC4959] SASL Initial Client Response, and + * UNSELECT [RFC3691]. ####################################################################### |