From: Steve Youngs <youngs@xemacs.org>
Subject: Re: Request: ding subscribers' group parameter
Date: Sat, 04 Aug 2001 00:45:42 +1000 [thread overview]
Message-ID: <microsoft-free.x4wv4lyzft.fsf@slackware.mynet.pc> (raw)
In-Reply-To: <or66c5zqg0.fsf@feijoada.lsd.ic.unicamp.br> (Alexandre Oliva's message of "03 Aug 2001 02:02:23 -0300")
|--==> "AO" == Alexandre Oliva <oliva@lsd.ic.unicamp.br> writes:
AO> On Jul 31, 2001, Karl Kleinpaste <karl@charcoal.com> wrote:
>>Could folks who subscribe here prettyplease put this parameter in
>>the group you use for the list?
>>(to-address . "ding@gnus.org")
>>It will prevent generation of private duplicates when `f'ollowing up
>>to the list.
AO> I actually prefer to be explicitly Cc:ed even when posting to the
AO> list, because my Score rules will highlight messages addressed to me,
AO> so I don't have to explicitly increase the score of the thread and
AO> hope for the best.
Why not simply increase the score of your Message-ID? Works well for me.
,----[ C-h C-i gnus RET m scoring RET m followTAB RET ]
| If you look closely at your own `Message-ID', you'll notice that the
| first two or three characters are always the same. Here's two of mine:
|
| <x6u3u47icf.fsf@eyesore.no>
| <x6sp9o7ibw.fsf@eyesore.no>
|
| So "my" ident on this machine is `x6'. This can be exploited--the
| following rule will raise the score on all followups to myself:
|
| ("references"
| ("<x6[0-9a-z]+\\.fsf\\(_-_\\)?@.*eyesore\\.no>"
| 1000 nil r))
`----
--
|---<Steve Youngs>---------------<GnuPG KeyID: 9E7E2820>---|
| XEmacs - It's not just an editor. |
| It's a way of life. |
|------------------------------------<youngs@xemacs.org>---|
next prev parent reply other threads:[~2001-08-03 14:45 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 [this message]
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
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=microsoft-free.x4wv4lyzft.fsf@slackware.mynet.pc \
--to=youngs@xemacs.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).