From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.general/19963 Path: main.gmane.org!not-for-mail From: Hrvoje Niksic Newsgroups: gmane.emacs.gnus.general Subject: Re: Mime-Version and no Content-Type Date: 19 Dec 1998 20:30:29 +0100 Sender: owner-ding@hpc.uh.edu Message-ID: References: <86pv9grln3.fsf@ponoka.battleriver.com> NNTP-Posting-Host: coloc-standby.netfonds.no Mime-Version: 1.0 X-Trace: main.gmane.org 1035158226 14354 80.91.224.250 (20 Oct 2002 23:57:06 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Sun, 20 Oct 2002 23:57:06 +0000 (UTC) Return-Path: Original-Received: from karazm.math.uh.edu (karazm.math.uh.edu [129.7.128.1]) by sclp3.sclp.com (8.8.5/8.8.5) with ESMTP id OAA20050 for ; Sat, 19 Dec 1998 14:31:01 -0500 (EST) Original-Received: from sina.hpc.uh.edu (lists@Sina.HPC.UH.EDU [129.7.3.5]) by karazm.math.uh.edu (8.9.1/8.9.1) with ESMTP id NAB06673; Sat, 19 Dec 1998 13:30:50 -0600 (CST) Original-Received: by sina.hpc.uh.edu (TLB v0.09a (1.20 tibbs 1996/10/09 22:03:07)); Sat, 19 Dec 1998 13:30:55 -0600 (CST) Original-Received: from sclp3.sclp.com (root@sclp3.sclp.com [204.252.123.139]) by sina.hpc.uh.edu (8.7.3/8.7.3) with ESMTP id NAA15412 for ; Sat, 19 Dec 1998 13:30:46 -0600 (CST) Original-Received: from jagor.srce.hr (hniksic@jagor.srce.hr [161.53.2.130]) by sclp3.sclp.com (8.8.5/8.8.5) with ESMTP id OAA20040 for ; Sat, 19 Dec 1998 14:30:37 -0500 (EST) Original-Received: (from hniksic@localhost) by jagor.srce.hr (8.9.0/8.9.0) id UAA11628; Sat, 19 Dec 1998 20:30:29 +0100 (MET) Original-To: ding@gnus.org X-Attribution: Hrvoje X-Face: &{dT~)Pu6V<0y?>3p$;@vh\`C7xB~A0T-J%Og)J,@-1%q6Q+, gs<-9M#&`I8cJp2b1{vPE|~+JE+gx;a7%BG{}nY^ehK1"q#rG O,Rn1A_Cy%t]V=Brv7h writes: > > Yes, but the very same RFC explicitly states that all header names > > are case-insensitive. > > Oh come on, who reads documentation? Anyone who wants their mail reader *not* to be totally broken. Has anyone provided a specific example of a mail reader known to be broken that way? > Isn't the real concern here providing for broken mail readers that > have been programmed ``by example''. The example is provided by the very documentation you claim noone to read. Please get my point right here: I *prefer* `MIME-Version' to `Mime-Version'; I've even sent out a patch that changes what message.el emits, but I want things named correctly. Emitting MIME-Version vs. emitting Mime-Version is aesthetics. Parsing MIME-Version but not parsing Mime-Version is brokenness. If there is a mailer that parses internet headers case-sensitively, it will break before it goes out of the house. > The *safest* thing to do is probably to use the capitalization shown > in the MIME RFCs in outgoing messages. I don't think the aesthetics > of it are all that relevant, Of course it is; aestheics is the reason why that particular case was used in the RFCs.