From: John Griffith <griffith@sfs.nphil.uni-tuebingen.de>
Subject: Re: Moving & suppressing
Date: 02 Aug 1996 14:20:13 +0200 [thread overview]
Message-ID: <tjohkugepu.fsf@sfs.nphil.uni-tuebingen.de> (raw)
In-Reply-To: Greg Stark's message of 02 Aug 1996 04:48:12 -0400
>>>>> "GS" == Greg Stark <gsstark@MIT.EDU> writes:
GS> While trying to evangalize a bit someone asked if Gnus could
GS> prevent them from seeing the same e-mail message twice even if
GS> the message-id's weren't available.
GS> This would be possible if we hashed the entire article, or
GS> even just the length and the first block of the article and
GS> saved that as a kind of pseudo-message-id. This really would
GS> be pretty nice, even i often see the same mail message on
GS> multiple lists that i read via mail archives, and often these
GS> archives don't retain the message-id's (i disagree with that
GS> as well of course, but Gnus should be general enough to not
GS> assume all the backends are news or mail. Some backends won't
GS> have any concept of message-id.)
I think this would be nice as well, but difficult. One problem with
this is that some lists add other junk to the beginnings and ends of
such messages, like "Forwarded through the blah list", or at least
extra white space. Leading white space could be ignored when hashing,
but the other junk would be more problematic. Other times messages
are embbeded in some kind of digest, so the parts of the digest would
have to be compared.
next prev parent reply other threads:[~1996-08-02 12:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1996-08-01 21:19 Lars Magne Ingebrigtsen
1996-08-02 8:48 ` Greg Stark
1996-08-02 12:20 ` John Griffith [this message]
1996-08-02 13:55 ` Duplicate messages with dissimilar Message-IDs Richard Pieri
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=tjohkugepu.fsf@sfs.nphil.uni-tuebingen.de \
--to=griffith@sfs.nphil.uni-tuebingen.de \
/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).