* Re: Thread and Followups scoring rules.
[not found] <mailman.23796.1365458413.855.info-gnus-english@gnu.org>
@ 2013-08-01 12:22 ` Lars Magne Ingebrigtsen
0 siblings, 0 replies; 2+ messages in thread
From: Lars Magne Ingebrigtsen @ 2013-08-01 12:22 UTC (permalink / raw)
To: Oleksandr Gavenko; +Cc: info-gnus-english
Oleksandr Gavenko <gavenkoa@gmail.com> writes:
> So I can put to all.SCORE:
>
> (("Followup"
> ("gavenkoa@gmail.com" 1000 nil s)
> ("Oleksandr Gavenkoa" 1000 nil s)))
>
> How this differ from:
>
> (("references"
> ("gavenkoa@gmail.com" 1000 nil s)
> ("Oleksandr Gavenkoa" 1000 nil s)))
The former, er, does what the manual says. It creates new entries based
on previous entries so that scoring happens even if the References
header is trimmed.
> Seems that this paragraph document 'I/L f/t' commands?
Yes.
--
(domestic pets only, the antidote for overdose, milk.)
No Gnus T-Shirt for sale: http://ingebrigtsen.no/no.php
^ permalink raw reply [flat|nested] 2+ messages in thread
* Thread and Followups scoring rules.
@ 2013-04-08 21:44 Oleksandr Gavenko
0 siblings, 0 replies; 2+ messages in thread
From: Oleksandr Gavenko @ 2013-04-08 21:44 UTC (permalink / raw)
To: info-gnus-english
This part of (info "(gnus)Score File Format") very hard to understand:
Six keys are supported by this alist:
`STRING'
If the key is a string, it is the name of the header to perform the
match on. Scoring can only be performed on these eight headers:
`From', `Subject', `References', `Message-ID', `Xref', `Lines',
`Chars' and `Date'. In addition to these headers, there are three
...
down group entry _considerably_. The final "header" you can score
on is `Followup'. These score entries will result in new score
...
Following this key is an arbitrary number of score entries, where
each score entry has one to four elements.
...
4. If the fourth element is present, it should be a symbol--the
"type element". This element specifies what function should
be used to see whether this score entry matches the article.
What match types that can be used depends on what header you
wish to perform the match on.
...
"Followup"
This match key is somewhat special, in that it will
match the `From' header, and affect the score of not
only the matching articles, but also all followups to
the matching articles. This allows you e.g. increase
the score of followups to your own articles, or decrease
the score of followups to the articles of some known
trouble-maker. Uses the same match types as the `From'
header uses. (Using this match key will lead to
creation of `ADAPT' files.)
"Thread"
This match key works along the same lines as the
`Followup' match key. If you say that you want to score
on a (sub-)thread started by an article with a
`Message-ID' X, then you add a `thread' match. This
will add a new `thread' match for each article that has
X in its `References' header. (These new `thread'
matches will use the `Message-ID's of these matching
articles.) This will ensure that you can raise/lower
the score of an entire thread, even though some articles
in the thread may not have complete `References'
headers. Note that using this may lead to
nondeterministic scores of the articles in the thread.
(Using this match key will lead to creation of `ADAPT'
files.)
So I can put to all.SCORE:
(("Followup"
("gavenkoa@gmail.com" 1000 nil s)
("Oleksandr Gavenkoa" 1000 nil s)))
How this differ from:
(("references"
("gavenkoa@gmail.com" 1000 nil s)
("Oleksandr Gavenkoa" 1000 nil s)))
Seems that this paragraph document 'I/L f/t' commands?
Are there any useful usage of 'Followup' and 'Thread' as permanent setting in
all.SCORE?
--
Best regards!
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2013-08-01 12:22 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
[not found] <mailman.23796.1365458413.855.info-gnus-english@gnu.org>
2013-08-01 12:22 ` Thread and Followups scoring rules Lars Magne Ingebrigtsen
2013-04-08 21:44 Oleksandr Gavenko
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).