From: David Z Maze <dmaze@mit.edu>
Subject: Re: spam.el/spam-stat checks in non-mail groups
Date: Sat, 23 Aug 2003 10:07:13 -0400 [thread overview]
Message-ID: <877k54lb72.fsf@everett.mit.edu> (raw)
In-Reply-To: <878yplwl2u.fsf@everett.mit.edu>
[-- Attachment #1: Type: text/plain, Size: 503 bytes --]
David Z Maze <dmaze@mit.edu> writes:
> Ted Zlatanov <tzz@lifelogs.com> writes:
>
>> You can't currently do spam checks on unseen messages in a newsgroup.
>>
>> It should be possible though, by running spam-split on every unseen
>> message at summary entry and checking if the output is equal to
>> spam-split-group (remember that the ifile backend, for instance, will
>> output a valid group name for non-spam so you can't just check for a
>> string).
>
> Hmm, like this?
This seems a little better:
[-- Attachment #2: Type: application/emacs-lisp, Size: 531 bytes --]
[-- Attachment #3: Type: text/plain, Size: 642 bytes --]
Having a little more documentation on what all of these hooks are and
what you can do from where would be useful, too.
gnus-summary-mark-article just doesn't work from
gnus-select-group-hook (invoking duplicate suppression fails because
gnus-data hasn't been built), but modifying the gnus-newsgroup-* lists
directly is tricky.
> I should probably use gnus-newsgroup-unseen rather than
> gnus-newsgroup-articles. But for a first pass, this appears to at
> least be close.
--
David Maze dmaze@mit.edu http://www.mit.edu/~dmaze/
"Theoretical politics is interesting. Politicking should be illegal."
-- Abra Mitchell
prev parent reply other threads:[~2003-08-23 14:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87ekzealuw.fsf@everett.mit.edu>
2003-08-22 10:31 ` Ted Zlatanov
2003-08-22 19:26 ` David Z Maze
2003-08-23 14:07 ` David Z Maze [this message]
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=877k54lb72.fsf@everett.mit.edu \
--to=dmaze@mit.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).