From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.general/21516 Path: main.gmane.org!not-for-mail From: Russ Allbery Newsgroups: gmane.emacs.gnus.general Subject: Re: forwarding as text rather than MIME? Date: 25 Feb 1999 02:39:01 -0800 Sender: owner-ding@hpc.uh.edu Message-ID: References: <87hfsnl7ys.fsf@graaff.xs4all.nl> <87lnhtcstr.fsf@graaff.xs4all.nl> <87k8xb1r6t.fsf@pc-hrvoje.srce.hr> <87d832uyf9.fsf@pc-hrvoje.srce.hr> <87zp66thv2.fsf@pc-hrvoje.srce.hr> NNTP-Posting-Host: coloc-standby.netfonds.no X-Trace: main.gmane.org 1035159604 23350 80.91.224.250 (21 Oct 2002 00:20:04 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Mon, 21 Oct 2002 00:20:04 +0000 (UTC) Return-Path: Original-Received: from fisher.math.uh.edu (fisher.math.uh.edu [129.7.128.35]) by sclp3.sclp.com (8.8.5/8.8.5) with ESMTP id FAA29057 for ; Thu, 25 Feb 1999 05:40:19 -0500 (EST) Original-Received: from sina.hpc.uh.edu (lists@Sina.HPC.UH.EDU [129.7.3.5]) by fisher.math.uh.edu (8.9.1/8.9.1) with ESMTP id EAB25590; Thu, 25 Feb 1999 04:39:18 -0600 (CST) Original-Received: by sina.hpc.uh.edu (TLB v0.09a (1.20 tibbs 1996/10/09 22:03:07)); Thu, 25 Feb 1999 04:39: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 EAA14566 for ; Thu, 25 Feb 1999 04:39:46 -0600 (CST) Original-Received: from windlord.stanford.edu (windlord.Stanford.EDU [171.64.12.23]) by sclp3.sclp.com (8.8.5/8.8.5) with SMTP id FAA29052 for ; Thu, 25 Feb 1999 05:39:37 -0500 (EST) Original-Received: (qmail 1868 invoked by uid 50); 25 Feb 1999 10:39:02 -0000 Original-To: ding@gnus.org In-Reply-To: Per Abrahamsen's message of "23 Feb 1999 19:32:21 +0100" Original-Lines: 50 X-Mailer: Gnus v5.4.66/Emacs 19.34 Precedence: list X-Majordomo: 1.94.jlt7 Xref: main.gmane.org gmane.emacs.gnus.general:21516 X-Report-Spam: http://spam.gmane.org/gmane.emacs.gnus.general:21516 Per Abrahamsen writes: > Hrvoje Niksic writes: >> It didn't use MIME. MIME is frowned upon in most news hierarchies. >> Toni summed it up pretty well. > *Unreadable* MIME is frowned upon. I don't think message/rfc822 is > particularily unreadable. Not that this is most hierarchies, but as for one particular fairly small hierarchy, says: | No binaries: "Usenet is Text" | ----------------------------- | | This isn't 1985. There are plenty of ways to exchange images and | software without hiding them in text. | | No subhierarchy can allow posts of binaries. If necessary, a separate | "bin.*" hierarchy will be created for this purpose. | | HTML and other verbose rich text formats are binaries. The only allowed | MIME types are: none (in which case the message must be in ISO8859.1, | since there must be a default and that's one that'll cover most of the | likely traffic), or: | | MIME-Version: 1.0 | Content-Type: text/plain; charset= OR multipart/signed | Content-Transfer-Encoding: 8bit OR 7bit | | If the Content-type is multipart/signed, then the parts may be: | | Content-Type: text/plain | Content-Type: application/pgp-signature At the time we wrote this, there was full justification for being this strict (and some similar policies are reflected in Cleannews filters and other similar places). Nowadays, I think it would probably be worth letting up on that to a large degree, but in the meantime I know there are lots of other moderated groups and smaller hierarchies that have set up similar policies. A way to revert to the old forwarding method is really necessary for those places for at least a little longer. Remember, MIME implementations have sucked so hard to date that everyone's still in shell shock from them and there are a lot of engrained reflex reactions. It's going to take a year or two of available non-sucking MIME implementations before this will change. -- Russ Allbery (rra@stanford.edu)