From: David Z Maze <dmaze@MIT.EDU>
Subject: Re: Trouble with spam.el and ifile
Date: Wed, 08 Jan 2003 11:07:04 -0500 [thread overview]
Message-ID: <y68n0mb39sn.fsf@multics.mit.edu> (raw)
In-Reply-To: <4nfzs3llqx.fsf@lockgroove.bwh.harvard.edu> (Ted Zlatanov's message of "Wed, 08 Jan 2003 10:11:34 -0500")
Ted Zlatanov <tzz@lifelogs.com> writes:
> On Tue, 07 Jan 2003, dmaze@MIT.EDU wrote:
>> spam-summary-prepare-exit, eh? That has
>>
>> ;; Only for spam groups, we expire and maybe move articles
>> (when (spam-group-spam-contents-p gnus-newsgroup-name)
>> (spam-mark-spam-as-expired-and-move-routine
>> (gnus-parameter-spam-process-destination gnus-newsgroup-name)))
>>
>> ...but that seems to be the opposite behavior from what I expect
>
> The behavior made sense to me at the time, but I see what you mean and
> my original thought was wrong. Perhaps it should be either reversed
> to apply to groups that are not spam (ham + unclassified), or *all*
> groups should have their spam-marked articles processed by
> spam-mark-spam-as-expired-and-move-routine. Should I pick one or the
> other, or make it yet another user option?
Picking one or the other is probably fine. Reversing the sense of the
test makes sense to me.
>> -- Is there any way to specify a group as a ham group besides group
>> parameters? I want every nnml group except my spam group to be
>> ham, but not groups in other backends, and my topic hierarchy
>> mixes news, mail, and other things. Setting ham on a per-group
>> basis is prohibitive with several hundred nnml groups and
>> automatic group generation from split methods.
>
> I'm not sure what other way to provide. You can already do it by
> regex (which should be able to do an exception). How would you
> suggest handling your case? A function hook?
By regex would be great, but I don't know which variable to set. (By
regex is even better if spamness overrides hamness, since then
"nnml:.*" can be ham.) In particular,
(defun spam-group-ham-contents-p (group)
(if (stringp group)
(memq 'gnus-group-spam-classification-ham
(gnus-parameter-spam-contents group))
nil))
doesn't do any obvious testing of group against a regex;
gnus-group-spam-contents-p at least tests if the group is a member of
spam-junk-mailgroups. *pause* *enlightenment* I want to set
(setq gnus-spam-newsgroup-contents
'(("nnml:.*" gnus-group-spam-classification-ham)
("nnml:mail.misc.spam" gnus-group-spam-classification-spam)))
since it looks like the magic in gnus-define-group-parameter picks the
last matching regexp from the alist. Probably (gnus)Filtering Spam
Using spam.el should talk about this; now that I think I have some
understanding, would you like me to write up some text?
--
David Maze dmaze@mit.edu http://www.mit.edu/~dmaze/
"Theoretical politics is interesting. Politicking should be illegal."
-- Abra Mitchell
next prev parent reply other threads:[~2003-01-08 16:07 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-07 16:52 David Z Maze
2003-01-07 19:47 ` Ted Zlatanov
2003-01-07 21:05 ` David Z Maze
2003-01-07 22:07 ` Ted Zlatanov
2003-01-07 22:32 ` David Z Maze
2003-01-07 22:42 ` David Z Maze
2003-01-08 4:55 ` Ted Zlatanov
2003-01-08 15:11 ` Ted Zlatanov
2003-01-08 16:07 ` David Z Maze [this message]
2003-01-08 16:15 ` David Z Maze
2003-01-08 16:25 ` Ted Zlatanov
2003-01-08 16:18 ` Ted Zlatanov
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=y68n0mb39sn.fsf@multics.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).