From: Ted Zlatanov <tzz@lifelogs.com>
Subject: Re: help with spam.el
Date: Mon, 24 Mar 2003 11:31:26 -0500 [thread overview]
Message-ID: <4n7kaopvz5.fsf@lockgroove.bwh.harvard.edu> (raw)
In-Reply-To: <kfvfy963bf.fsf@shaoz.activesky.com.au>
On Mon, 24 Mar 2003, shaoz@activesky.com wrote:
> 1) according to documentation, all articles in spam group are
> considered to be spam and they get the $ mark when entering the
> group. I have set both spam-junk-groups and
> gnus-spam-newsgroup-contents to nnfolder+archive:spam. But when
> entering group, all articles are marked with E, is this the right
> behaviour?
In the spam group, *new* articles will have the spam mark. You are
transferring spam articles from another group automatically to the
spam group, so they are automatically expired already (since they were
spam-processed in the original group). Otherwise, they would get
processed as spam twice, which would be a bad thing.
Generally, the spam mark is something an article will only see once
briefly, before it's processed as spam and marked as expired.
> 2) So far, I have to mark every spam message manually. My spam group
> has already over 300 messages. But I have not got any marked
> automatically by gnus yet, am I missing another step or config?
I'm not sure what you mean by "automatically." What do you expect to
happen, and what happens instead?
You had this last time:
'(gnus-spam-newsgroup-contents (quote (("spam" gnus-group-spam-classification-spam) ("~/Mail/inbox" gnus-group-spam-classification-ham))))
'(gnus-spam-process-destinations (quote (("nnimap*" "spam"))))
'(gnus-spam-process-newsgroups (quote (("spam" (gnus-group-spam-exit-processor-ifile)) ("nnimap*" (gnus-group-ham-exit-processor-ifile)))))
'(spam-junk-mailgroups (quote ("spam")))
'(spam-use-ifile t))
Looking at your settings, you have unqualified group names for almost
all the spam.el parameters - make sure you use ".*spam" if you want
to match all folders that end with "spam", for instance. Also,
"nnimap*" means "'nnima' followed by 0 or more letters 'p'," which is
almost certainly not what you meant - you want "nnimap.*" I think.
I'm still somewhat cautious about a folder called "~/Mail/inbox" by
the way. Are you sure that's correct?
If you have trouble setting the regular expressions you need, you can
try using `G c' on a topic (if you use topics and have all your
related groups under the same topic), or `G c' on a particular group
in order to experiment with particular settings for spam/ham exit
processors and contents classification.
Thanks
Ted
next parent reply other threads:[~2003-03-24 16:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <kfisuevghb.fsf@shaoz.activesky.com.au>
[not found] ` <4nhe9yeykj.fsf@lockgroove.bwh.harvard.edu>
[not found] ` <kfvfy963bf.fsf@shaoz.activesky.com.au>
2003-03-24 16:31 ` Ted Zlatanov [this message]
[not found] ` <kfptoflzbj.fsf@shaoz.activesky.com.au>
[not found] ` <4nvfy6850a.fsf@lockgroove.bwh.harvard.edu>
2003-03-26 23:30 ` Shao Zhang
[not found] ` <4nu1do4sb6.fsf@lockgroove.bwh.harvard.edu>
2003-03-28 3:54 ` Shao Zhang
2003-04-07 20:00 ` Ted Zlatanov
2003-03-28 3:43 ` Shao Zhang
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=4n7kaopvz5.fsf@lockgroove.bwh.harvard.edu \
--to=tzz@lifelogs.com \
/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).