From: dreschs@mpd.tandem.com (Sten Drescher)
Subject: Re: Resending
Date: 06 Dec 1995 12:08:46 -0600 [thread overview]
Message-ID: <55wx8akqtt.fsf@galil.austnsc.tandem.com> (raw)
In-Reply-To: davidk@lysator.liu.se's message of 05 Dec 1995 10:52:37 +0100
davidk@lysator.liu.se (David K}gedal) said:
DK> This patch fixes the most serious bugs in the resending code in
DK> 0.18, making it almost useful...
DK> It also fixes a bug that made Gnus always insert a Sender header,
DK> even when it was not supposed to.
DK> I still get the headers "Resent-Sender" and "Resent-Message-ID",
DK> which I'm not too fond of, at least not the first.
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. 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).
--
#include <disclaimer.h> /* 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
next prev parent reply other threads:[~1995-12-06 18:08 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 ` Sten Drescher [this message]
1995-12-08 16:45 ` Resending David K}gedal
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=55wx8akqtt.fsf@galil.austnsc.tandem.com \
--to=dreschs@mpd.tandem.com \
/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).