IETF Logo Mail Archive

Re: [imap5] Standardized error messages

Peter Mogensen <apm@one.com> Tue, 21 October 2008 17:26 UTC

Return-Path: <imap5-bounces@ietf.org>
X-Original-To: imap5-archive@ietf.org
Delivered-To: ietfarch-imap5-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D48333A6A59; Tue, 21 Oct 2008 10:26:07 -0700 (PDT)
X-Original-To: imap5@core3.amsl.com
Delivered-To: imap5@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4CDCE3A6A42 for <imap5@core3.amsl.com>; Tue, 21 Oct 2008 10:26:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id d6bVZq8cYajC for <imap5@core3.amsl.com>; Tue, 21 Oct 2008 10:26:05 -0700 (PDT)
Received: from kontorsmtp.b-one.net (kontorsmtp.b-one.net [195.47.247.217]) by core3.amsl.com (Postfix) with ESMTP id 8731D3A6B80 for <imap5@ietf.org>; Tue, 21 Oct 2008 10:26:05 -0700 (PDT)
Received: from [192.168.44.103] (x1-6-00-0f-66-c7-92-26.k358.webspeed.dk [80.167.71.239]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by kontorsmtp.b-one.net (Postfix) with ESMTP id 1F6FBD317245; Tue, 21 Oct 2008 17:27:10 +0000 (UTC)
Message-ID: <48FE10EE.1030009@one.com>
Date: Tue, 21 Oct 2008 19:27:10 +0200
From: Peter Mogensen <apm@one.com>
User-Agent: Thunderbird 2.0.0.17 (X11/20080925)
MIME-Version: 1.0
To: Arnt Gulbrandsen <arnt@oryx.com>
References: <48FDED75.9050703@one.com> <U/wP4jc/WRmo1cfBxCa2XA.md5@lochnagar.oryx.com>
In-Reply-To: <U/wP4jc/WRmo1cfBxCa2XA.md5@lochnagar.oryx.com>
Cc: imap5@ietf.org
Subject: Re: [imap5] Standardized error messages
X-BeenThere: imap5@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "Discussion on drastically slimming-down IMAP." <imap5.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/imap5>, <mailto:imap5-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/imap5>
List-Post: <mailto:imap5@ietf.org>
List-Help: <mailto:imap5-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/imap5>, <mailto:imap5-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: imap5-bounces@ietf.org
Errors-To: imap5-bounces@ietf.org

Arnt Gulbrandsen wrote:
> Please read RFC 5255

Oh... hadn't seen.
It's of course better wrt. i18n than RFC3501, but IMHO it also servers 
to make the matter worse wrt. server-responses not being the same across 
implementations. Now you have several languages for which the response 
could differ differently.

> and draft-gulbrandsen-imap-response-codes, and see 
> what you think.

Better... although I'm not sure it's a good idea to merge error-codes 
and status info (like UNSEEN,UIDNEXT...) into the same namespace.

/Peter

_______________________________________________
imap5 mailing list
imap5@ietf.org
https://www.ietf.org/mailman/listinfo/imap5

v2.23.0 | Report a Bug | By Email