Gnus development mailing list
 help / color / mirror / Atom feed
From: davidk@lysator.liu.se (David K}gedal)
Subject: Re: Resending
Date: 08 Dec 1995 17:45:52 +0100	[thread overview]
Message-ID: <jp3favqzb3.fsf@tina.lysator.liu.se> (raw)
In-Reply-To: dreschs@mpd.tandem.com's message of 06 Dec 1995 12:08:46 -0600

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.

Yes, I use Gnus to read this, so I only have to see it once, but
aren't you talking about Message-ID? Where does Resent-Message-ID come
into all this?

>Also, Resent-Sender
>is also in the RFC as an originator field, although discouraged then it
>matches Resent-From (which it would usually be in this case).

Well, I think that Gnus should at least hide this header, as it does
for Sender.

-- 
David Kågedal     Lysator Academic Computer Society       davidk@lysator.liu.se
http://www.lysator.liu.se/~davidk/                              +46-13 17 65 89


  reply	other threads:[~1995-12-08 16:45 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1995-12-05  9:52 Resending David K}gedal
1995-12-06 18:08 ` Resending Sten Drescher
1995-12-08 16:45   ` David K}gedal [this message]
1995-12-08 20:09     ` Resending Sten Drescher
1995-12-10 15:15       ` Resending Lars Magne Ingebrigtsen
  -- strict thread matches above, loose matches on Subject: below --
1995-12-04  4:18 Resending Lars Magne Ingebrigtsen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=jp3favqzb3.fsf@tina.lysator.liu.se \
    --to=davidk@lysator.liu.se \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).