Gnus development mailing list
 help / color / mirror / Atom feed
From: Russ Allbery <eagle@cyclone.Stanford.EDU>
Subject: Red Gnus: Posted & e-mailed detection
Date: Tue, 19 Mar 1996 07:30:29 -0800 (PST)	[thread overview]
Message-ID: <199603191530.HAA10695@cyclone.Stanford.EDU> (raw)

(Forgive me if this has already been suggested; I haven't been paying
extremely close attention to the various proposed features.)

I highly dislike getting copies of posts via e-mail when they aren't
marked as such in any standard fashion, but an ever-growing number of
people seen determined to keep doing that.  As such, it would be nice if
Gnus could detect such messages and tell me about them.

It occurred to me today that one way to do that which would work for any
newsreader that generated its own message IDs (so that the ID for the
mailed and posted copies would be identical) would be to just send an
XPATH request to the news server for each mail message, or perhaps for
each mail message in certain mail groups (I wouldn't have to check all the
mailing list traffic that I get, but I'd like to check each personal
message).  If it returns something, then the message was also posted.

It could also just be a new function, so people would have to explicitly
check.  That would probably be the best way of doing it.

This assumes that the message has already shown up on your news server by
the time you read the mail message, so it's not quite ideal, but it's an
idea anyway, and for those of us with fast news feeds, it would be
reasonably effective.  If you already have a server connection open, it
should be fairly fast as well.

Anyway, I thought I'd throw out the idea and see what people have to say
about it.

-- 
Russ Allbery (rra@cs.stanford.edu)      <URL:http://www.eyrie.org/~eagle/>


             reply	other threads:[~1996-03-19 15:30 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1996-03-19 15:30 Russ Allbery [this message]
1996-03-19 20:55 ` 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=199603191530.HAA10695@cyclone.Stanford.EDU \
    --to=eagle@cyclone.stanford.edu \
    /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).