From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.general/16981 Path: main.gmane.org!not-for-mail From: Lars Magne Ingebrigtsen Newsgroups: gmane.emacs.gnus.general Subject: Re: Those MIME requirements Date: 12 Sep 1998 08:10:47 +0200 Sender: owner-ding@hpc.uh.edu Message-ID: References: NNTP-Posting-Host: coloc-standby.netfonds.no X-Trace: main.gmane.org 1035155763 30999 80.91.224.250 (20 Oct 2002 23:16:03 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Sun, 20 Oct 2002 23:16:03 +0000 (UTC) Return-Path: Original-Received: from gizmo.hpc.uh.edu (gizmo.hpc.uh.edu [129.7.102.31]) by sclp3.sclp.com (8.8.5/8.8.5) with ESMTP id DAA29068 for ; Sat, 12 Sep 1998 03:03:45 -0400 (EDT) Original-Received: from sina.hpc.uh.edu (sina.hpc.uh.edu [129.7.3.5]) by gizmo.hpc.uh.edu (8.7.6/8.7.3) with ESMTP id BAF15194; Sat, 12 Sep 1998 01:34:48 -0500 Original-Received: by sina.hpc.uh.edu (TLB v0.09a (1.20 tibbs 1996/10/09 22:03:07)); Sat, 12 Sep 1998 02:02:05 -0500 (CDT) Original-Received: from sclp3.sclp.com (root@sclp3.sclp.com [209.195.19.139]) by sina.hpc.uh.edu (8.7.3/8.7.3) with ESMTP id CAA23407 for ; Sat, 12 Sep 1998 02:01:31 -0500 (CDT) Original-Received: from sparky.gnus.org (ppp011.uio.no [129.240.240.12]) by sclp3.sclp.com (8.8.5/8.8.5) with ESMTP id DAA29000 for ; Sat, 12 Sep 1998 03:01:19 -0400 (EDT) Original-Received: (from larsi@localhost) by sparky.gnus.org (8.8.5/8.8.5) id JAA08110; Sat, 12 Sep 1998 09:04:25 +0200 Mail-Copies-To: never X-Now-Reading: Ursula K. Le Guin's _Unlocking the Air and Other Stories_ Original-To: ding@gnus.org In-Reply-To: Hrvoje Niksic's message of "11 Sep 1998 20:10:58 +0200" User-Agent: Gnus/5.070028 (Pterodactyl Gnus v0.28) XEmacs/21.0 (Finnish Landrace) X-Face: &w!^oO~dS|}-P0~ge{$c!h\ writes: > > Currently, I don't do anything with Content-Disposition. Shouldn't > > display of elements be up to the recipient, and not the sender? > > The sender should be allowed to express a preference. For example, a > set of huge pictures attached to a message can be hazardous to insert > in the buffer. In this case, sender can ask the recipient not to > inline it. Or can't it? Yup. I've now made the automatic inlining functions respect the Content-Disposition header. -- (domestic pets only, the antidote for overdose, milk.) larsi@gnus.org * Lars Magne Ingebrigtsen