From: Steven L Baur <steve@miranova.com>
Subject: Removing the original of a duplicated message
Date: 01 May 1996 10:00:15 -0700 [thread overview]
Message-ID: <m24tq08h28.fsf@deanna.miranova.com> (raw)
Cc: linux-kernel@vger.rutgers.edu, linux-net@vger.rutgers.edu
Message-ID: <m2ohody2ks.fsf@totally-fudged-out-message-id>
Original-Message-Id: <199604251540.QAA03609@snowcrash.cymru.net>
Gnus-Warning: This is a duplicate of message <199604251540.QAA03609@snowcrash.cymru.net>
Is there any automatic method after eliminating an original message,
to modify the headers of a duplicate message to what they originally
were? Restated: when Gnus receives a duplicate message (as from a
crossposted message to two or more mailing lists, and you receive
both) I'd like to be able to eliminate what Gnus thinks is the
original message and keep only the duplicate, but have the duplicate
take back its original headers.
In the example headers given, that would mean erasing the bogus
Message-ID: field and restoring it from the Original-Message-Id:,
removing the Gnus-Warning: header, and updating the nnml .overview.
Gnus' handling of duplicated messages has bothered me for a long time
as more often than not the default behavior is inconvenient for me.
--
steve@miranova.com baur
Unsolicited commercial e-mail will be proofread for $250/hour.
Andrea Seastrand: For your vote on the Telecom bill, I will vote for anyone
except you in November.
next reply other threads:[~1996-05-01 17:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1996-05-01 17:00 Steven L Baur [this message]
1996-05-02 14:17 ` 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=m24tq08h28.fsf@deanna.miranova.com \
--to=steve@miranova.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).