From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.general/19942 Path: main.gmane.org!not-for-mail From: Hrvoje Niksic Newsgroups: gmane.emacs.gnus.general Subject: Re: Mime-Version and no Content-Type Date: 18 Dec 1998 04:41:55 +0100 Sender: owner-ding@hpc.uh.edu Message-ID: References: NNTP-Posting-Host: coloc-standby.netfonds.no Mime-Version: 1.0 X-Trace: main.gmane.org 1035158200 14178 80.91.224.250 (20 Oct 2002 23:56:40 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Sun, 20 Oct 2002 23:56:40 +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 WAA06269 for ; Thu, 17 Dec 1998 22:42:28 -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 VAB09383; Thu, 17 Dec 1998 21:42:17 -0600 (CST) Original-Received: by sina.hpc.uh.edu (TLB v0.09a (1.20 tibbs 1996/10/09 22:03:07)); Thu, 17 Dec 1998 21:42:20 -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 VAA28644 for ; Thu, 17 Dec 1998 21:42:11 -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 WAA06259 for ; Thu, 17 Dec 1998 22:42:03 -0500 (EST) Original-Received: (from hniksic@localhost) by jagor.srce.hr (8.9.0/8.9.0) id EAA16866; Fri, 18 Dec 1998 04:41:55 +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: > >> > Can you explain How your reasoning ran on that again? : ) > >> > >> Sure, Harry. No problem. > >> > >> First off, mime postdates rfc822 so it's not really appropriate > >> to be quoting rules from that rfc, however correct they might > >> be. This makes no sense, given that MIME is explicitly designed to fit into rfc822. > >> I don't have full references on this point, although it's quite > >> well known, but it appears that there are some mime > >> implementations which parse for the "mime" portion of > >> "MIME-Version" in upper case only, I don't consider this "well-known" at all. Never heard of it myself. > >> | draft-ietf-usefor-article-01 > >> | > >> | Header-names are case-insensitive. There is a preferred case > >> | convention, which posters and posting agents SHOULD use: > >> | each hyphen-separated "word" has its initial letter (if any) > >> | in uppercase and the rest in lowercase, except that some > >> | abbreviations have all letters uppercase (e.g. "Message-ID" > >> | and "MIME-Version"). As I said: aesthetics, pure and simple.