Gnus development mailing list
 help / color / mirror / Atom feed
From: Alexandre Oliva <oliva@lsd.ic.unicamp.br>
Cc: ding@gnus.org
Subject: Re: Request: ding subscribers' group parameter
Date: 04 Aug 2001 00:37:09 -0300	[thread overview]
Message-ID: <orzo9g4hsq.fsf@feijoada.lsd.ic.unicamp.br> (raw)
In-Reply-To: Russ Allbery's message of "03 Aug 2001 17:40:12 -0700"

On Aug  3, 2001, Russ Allbery <rra@stanford.edu> wrote:

> ("references"
>  ("<or[0-9a-z]+\.fsf\\(_-_\\)?@feijoada\\.lsd\\.ic\\.unicamp\\.br>"
>   200 nil r))

> Stick it in all.SCORE and you're all set.

> I've been using this technique for four or five years now at least.

Thanks, I've been using something very close to this for a few hours,
and I must admit it's far superior to the one that matches my e-mail
addresses in To: and Cc: "head"ers.  However, I've verified that it
doesn't work in two cases: (i) when the replier's MUA is too dumb to
set References: correctly (fortunately this is rare, but I do care
about e-mail I get from some of the people who choose to use such
broken MUAs) and (ii) it fails to highlight e-mail addressed to me in
my misc e-mail folder, which often helps me tell good e-mail from SPAM
that hides the addressees, which is the most common kind of SPAM in my
statistics.


Anyway, is there any reason why gnus doesn't offer "to" and "cc" as
score strings?  I would find this quite useful, and I don't understand
why it hasn't done before.  Is it just because To: and Cc: don't make
much sense for news?

-- 
Alexandre Oliva   Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer                  aoliva@{cygnus.com, redhat.com}
CS PhD student at IC-Unicamp        oliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist    *Please* write to mailing lists, not to me


  reply	other threads:[~2001-08-04  3:37 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-31 15:13 Karl Kleinpaste
2001-07-31 16:15 ` Paul Jarc
2001-07-31 18:42   ` Colin Walters
2001-07-31 20:08     ` Paul Jarc
2001-07-31 21:26   ` Kai Großjohann
2001-08-17  9:56     ` Lars Magne Ingebrigtsen
2001-08-17 11:37       ` Kai Großjohann
2001-08-17 12:08         ` Lars Magne Ingebrigtsen
2001-07-31 21:37   ` Karl Kleinpaste
2001-07-31 21:50     ` Kai Großjohann
2001-07-31 21:56       ` Karl Kleinpaste
2001-07-31 22:44         ` Kai Großjohann
2001-07-31 23:01           ` Karl Kleinpaste
2001-07-31 23:58             ` Nevin Kapur
2001-08-01 14:54           ` Steve Youngs
2001-08-01 15:40             ` Paul Jarc
2001-08-01 16:07               ` Karl Kleinpaste
2001-08-01 17:00                 ` Paul Jarc
2001-08-01 17:03                 ` Nuutti Kotivuori
2001-07-31 21:57     ` Paul Jarc
2001-08-01  9:58   ` Kai Großjohann
2001-08-01 15:34     ` Paul Jarc
2001-07-31 16:18 ` Kai Großjohann
2001-08-01 14:44 ` Steve Youngs
2001-08-02 12:37   ` gnus-mailing-list-mode (was: Request: ding subscribers' group parameter) Henrik Enberg
2001-08-02 15:06     ` Kai Großjohann
2001-08-17 10:01     ` Lars Magne Ingebrigtsen
2001-08-02 15:29   ` Request: ding subscribers' group parameter Paul Jarc
2001-08-03  4:38     ` Jochen Küpper
2001-08-03  5:02 ` Alexandre Oliva
2001-08-03 14:45   ` Steve Youngs
2001-08-03 20:59     ` Alexandre Oliva
2001-08-03 22:03       ` Kai Großjohann
2001-08-03 22:59         ` Alexandre Oliva
2001-08-03 23:08           ` Paul Jarc
2001-08-04  0:40       ` Russ Allbery
2001-08-04  3:37         ` Alexandre Oliva [this message]
2001-08-04 10:44           ` Florian Weimer
2001-08-04 11:32             ` Alexandre Oliva
2001-08-04 11:41           ` Kai Großjohann
2001-08-04 13:01           ` Karl Kleinpaste
2001-08-17 10:11             ` Lars Magne Ingebrigtsen
2001-08-03 15:17   ` Paul Jarc
2001-08-10 14:47 ` Per Abrahamsen

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=orzo9g4hsq.fsf@feijoada.lsd.ic.unicamp.br \
    --to=oliva@lsd.ic.unicamp.br \
    --cc=ding@gnus.org \
    /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).