29 lines
1.1 KiB
Plaintext
29 lines
1.1 KiB
Plaintext
MBOX-Line: From alexey.melnikov at isode.com Tue Dec 11 04:05:36 2012
|
|
To: imap-protocol@u.washington.edu
|
|
From: Alexey Melnikov <alexey.melnikov@isode.com>
|
|
Date: Fri Jun 8 12:34:49 2018
|
|
Subject: [Imap-protocol] Re: BINARY for broken MIME parts
|
|
In-Reply-To: <d1beb98e-c6b8-4464-b857-4820f367ff94@flaska.net>
|
|
References: <CDD9BF88-A87D-41CB-A668-E2A7FE5CFE20@iki.fi>
|
|
<50C0A8F4.4070405@isode.com>
|
|
<809DCB83-1507-4F6B-8B70-D86042569C46@iki.fi>
|
|
<CABa8R6tJV4iOjgckqLzEqLcdifRnVj6+g_7cB1vNd3YTgSt4pw@mail.gmail.com>
|
|
<d1beb98e-c6b8-4464-b857-4820f367ff94@flaska.net>
|
|
Message-ID: <50C72190.9040508@isode.com>
|
|
|
|
On 11/12/2012 11:55, Jan Kundr?t wrote:
|
|
> On Tuesday, 11 December 2012 07:16:35 CEST, Brandon Long wrote:
|
|
>> I would think [PARSE] would be more appropriate than UNKNOWN-CTE. Or
|
|
>> just stick with [ALERT].
|
|
>
|
|
> ALERT is reserved for situations which MUST be communicated to the
|
|
> user. If the IMAP server cannot decode a particular CTE, another
|
|
> response code shall be used -- this is a condition where the client
|
|
> shall make its decision on how to proceed, but definitely not by
|
|
> showing an ALERT to the user.
|
|
>
|
|
> Please, don't use ALERT for this.
|
|
+1.
|
|
|
|
|