Re: [Ltru] Re: [EAI] New draft for allowing UTF-8 in SMTP responses
Alexey Melnikov <alexey.melnikov@isode.com> Sun, 27 August 2006 14:27 UTC
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GHLbV-00058P-KP; Sun, 27 Aug 2006 10:27:13 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GHLbU-00058D-Ow; Sun, 27 Aug 2006 10:27:12 -0400
Received: from rufus.isode.com ([62.3.217.251]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GHLbT-0007so-8R; Sun, 27 Aug 2006 10:27:12 -0400
Received: from [172.16.1.99] (shiny.isode.com [62.3.217.250]) by rufus.isode.com via TCP (submission) with ESMTPA; Sun, 27 Aug 2006 15:26:38 +0100
Message-ID: <44F18DB8.4040601@isode.com>
Date: Sun, 27 Aug 2006 13:19:04 +0100
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.12) Gecko/20050915
X-Accept-Language: en-us, en
To: Tony Finch <dot@dotat.at>
Subject: Re: [Ltru] Re: [EAI] New draft for allowing UTF-8 in SMTP responses
References: <44E09667.8070704@isode.com> <6.0.0.20.2.20060818150743.097d4ec0@localhost> <Pine.LNX.4.64.0608211251060.5633@hermes-2.csi.cam.ac.uk> <003401c6c54d$18765640$6501a8c0@oemcomputer> <6AD3D4FD1D4C386BE716C69C@p3.JCK.COM> <44EC3A45.90201@alvestrand.no> <Pine.LNX.4.64.0608231231070.5633@hermes-2.csi.cam.ac.uk>
In-Reply-To: <Pine.LNX.4.64.0608231231070.5633@hermes-2.csi.cam.ac.uk>
MIME-version: 1.0
Content-type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-transfer-encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 25620135586de10c627e3628c432b04a
Cc: Greg Vaudreuil <gregv@lucent.com>, LTRU Working Group <ltru@ietf.org>, Addison Phillips <addison@yahoo-inc.com>, ima@ietf.org
X-BeenThere: ima@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "EAI \(Email Address Internationalization\)" <ima.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ima>, <mailto:ima-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ima>
List-Post: <mailto:ima@ietf.org>
List-Help: <mailto:ima-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ima>, <mailto:ima-request@ietf.org?subject=subscribe>
Errors-To: ima-bounces@ietf.org
Tony Finch wrote: >Addison says: > > >>Almost no one interacts with SMTP servers directly. >> >> >Of course they do, to the same extent that they interact with IMAP or POP >or HTTP servers - mediated by a user agent. > >From my point of view, and from the point of view of my colleagues on the >help desk, it would be much easier if MUAs did not try to impose their own >gloss on my servers' error messages (or do other stupid things like >truncate them). That way I can provide helpful text that explains what >went wrong, and/or a URL to help pages or a directory. > >The curre. b). Extend message/delivery-status to allow for 8bit data. RFC 3464 seem to disallow this: 2.1 The message/delivery-status content-type The message/delivery-status content-type is defined as follows: MIME type name: message MIME subtype name: delivery-status Optional parameters: none Encoding considerations: "7bit" encoding is sufficient and MUST be used to maintain readability when viewed by non-MIME mail readers. And RFC 2046 seem to advise against non-7bit encodings in message/*: 5.2.4. Other Message Subtypes MIME implementations must in general treat unrecognized subtypes of "message" as being equivalent to "application/octet-stream". Future subtypes of "message" intended for use with email should be restricted to "7bit" encoding. A type other than "message" should be used if restriction to "7bit" is not possible. Alexey P.S. However I still thing that encouraging servers to implement Enhanced Status Codes is a good idea. I would also like to work on response boilerplates. _______________________________________________ IMA mailing list IMA@ietf.org https://www1.ietf.org/mailman/listinfo/ima
- [EAI] New draft for allowing UTF-8 in SMTP respon… Alexey Melnikov
- Re: [Filtered!] [EAI] New draft for allowing UTF-… Tony Finch
- Re: [Filtered!] [EAI] New draft for allowing UTF-… Alexey Melnikov
- Re: [Filtered!] [EAI] New draft for allowing UTF-… Tony Finch
- Re: [EAI] New draft for allowing UTF-8 in SMTP re… Harald Alvestrand
- Re: [EAI] New draft for allowing UTF-8 in SMTP re… Alexey Melnikov
- Re: [EAI] New draft for allowing UTF-8 in SMTP re… Harald Alvestrand
- Re: [EAI] New draft for allowing UTF-8 in SMTP re… Tony Finch
- Re: [EAI] New draft for allowing UTF-8 in SMTP re… Alexey Melnikov
- Re: [EAI] New draft for allowing UTF-8 in SMTP re… Harald Alvestrand
- Re: [EAI] New draft for allowing UTF-8 in SMTP re… Martin Duerst
- Re: [EAI] New draft for allowing UTF-8 in SMTP re… Tony Finch
- Re: [Ltru] Re: [EAI] New draft for allowing UTF-8… Randy Presuhn
- Re: [EAI] New draft for allowing UTF-8 in SMTP re… Alexey Melnikov
- Re: [Ltru] Re: [EAI] New draft for allowing UTF-8… John C Klensin
- Re: [Ltru] Re: [EAI] New draft for allowing UTF-8… John C Klensin
- Re: [Ltru] Re: [EAI] New draft for allowing UTF-8… Charles Lindsey
- Re: [EAI] New draft for allowing UTF-8 in SMTP re… Charles Lindsey
- Re: [Ltru] Re: [EAI] New draft for allowing UTF-8… Harald Alvestrand
- Re: [Ltru] Re: [EAI] New draft for allowing UTF-8… Addison Phillips
- Re: [Ltru] Re: [EAI] New draft for allowing UTF-8… Tony Finch
- Re: [EAI] New draft for allowing UTF-8 in SMTP re… Martin Duerst
- Re: [Ltru] Re: [EAI] New draft for allowing UTF-8… Martin Duerst
- Re: [EAI] New draft for allowing UTF-8 inSMTP res… Frank Ellermann
- Re: [Ltru] Re: [EAI] New draft for allowing UTF-8… Charles Lindsey
- Re: [Ltru] Re: [EAI] New draft for allowing UTF-8… Alexey Melnikov