From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.general/4318 Path: main.gmane.org!not-for-mail From: dreschs@mpd.tandem.com (Sten Drescher) Newsgroups: gmane.emacs.gnus.general Subject: Re: Resending Date: 08 Dec 1995 14:09:56 -0600 Organization: Tandem Computers Sender: dreschs@mpd.tandem.com Message-ID: <553favgvvv.fsf@galil.austnsc.tandem.com> References: <55wx8akqtt.fsf@galil.austnsc.tandem.com> NNTP-Posting-Host: coloc-standby.netfonds.no Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Trace: main.gmane.org 1035145079 29144 80.91.224.250 (20 Oct 2002 20:17:59 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Sun, 20 Oct 2002 20:17:59 +0000 (UTC) Cc: ding@ifi.uio.no Return-Path: ding-request@ifi.uio.no Original-Received: from ifi.uio.no (ifi.uio.no [129.240.64.2]) by miranova.com (8.6.11/8.6.9) with ESMTP id MAA23076 for ; Fri, 8 Dec 1995 12:55:23 -0800 Original-Received: from galil.austnsc.tandem.com (argyle.mpd.tandem.com [131.124.250.13]) by ifi.uio.no with ESMTP (8.6.11/ifi2.4) id for ; Fri, 8 Dec 1995 21:08:58 +0100 Original-Received: (from dreschs@localhost) by galil.austnsc.tandem.com (8.7.1/8.7.1) id OAA04802; Fri, 8 Dec 1995 14:09:59 -0600 (CST) Original-To: davidk@lysator.liu.se In-Reply-To: davidk@lysator.liu.se's message of 08 Dec 1995 17:45:52 +0100 Original-Lines: 41 Xref: main.gmane.org gmane.emacs.gnus.general:4318 X-Report-Spam: http://spam.gmane.org/gmane.emacs.gnus.general:4318 davidk@lysator.liu.se (David K}gedal) said: DK> dreschs@mpd.tandem.com (Sten Drescher) writes: >> Resent-Message-ID is in RFC 822 as a reference field, and it is a >> Good Thing - for example, I use procmail/formail to save 10KB of >> Message-IDs, and drop duplicates. The main use for this is in >> mailing lists - like right now. If you drop duplicates, you will see >> this once. If you don't, you'll see it twice - once from me, and >> once from the list. If you bounce a message to me, without >> alteration, I'd want it to be dropped if I've already received it >> elsewhere. DK> Yes, I use Gnus to read this, so I only have to see it once, but DK> aren't you talking about Message-ID? Where does Resent-Message-ID DK> come into all this? It's in RFC 822. But rereading the RFC, it doesn't work quite the way I thought it did (the original Message-ID should be untouched). Still, putting the Resent-Message-ID field in (which, like Message-ID, is optional in the RFC) is prolly a good thing, since the Resent- headers are supposed to parallel the normal headers. But a parallel question: goes Gnus know to supercede existing Resent- headers, either by prepending them with Also- or Old- (I prefer Also-), or simply stripping them out? I can easily imagine a message getting resent more than once, and: rfc822> 4.2. FORWARDING [...] rfc822> Note: In general, the "Resent-" fields should be treated as rfc822> containing a set of information that is independent of the set rfc822> of original fields. Information for one set should not rfc822> automatically be taken from the other. The interpretation of rfc822> multiple "Resent-" fields, of the same type, is undefined. -- #include /* Sten Drescher */ To get my PGP public key, send me email with your public key and Subject: PGP key exchange Key fingerprint = 90 5F 1D FD A6 7C 84 5E A9 D3 90 16 B2 44 C4 F3