From: Steinar Bang <sb@dod.no>
Subject: Re: How to load spam.el just for gmane reporting?
Date: Sun, 28 Sep 2003 00:39:11 +0200 [thread overview]
Message-ID: <87d6dl6els.fsf@doohan.bang.priv.no> (raw)
In-Reply-To: <yccad8sr4v5.fsf@orff.wc.cray.com>
>>>>> Ted Stern <stern+gnus@cray.com>:
[snip!]
> ;; Set up spam reporting
> (require 'spam)
> (require 'spam-report)
So spam-use-* is not neccessary? Perhaps the manual should be changed
to reflect this?
> I put all my Gmane groups in a single Topic. Then I customize group
> parameters for the Topic ("G p" on the "Gmane" topic line in the *Group*
> buffer):
> ((spam-process
> (gnus-group-spam-exit-processor-report-gmane)))
Hm... I can't (actually "won't") do it that way. But thanx for the
tip!
Putting spam-process into all gmane groups' group parameters, is too
much work, and is something I'd have to remember when creating new
groups.
So I guess I'll have to figure out how to set up the
gnus-spam-process-destinations variable.
I tried the following,
(setq gnus-spam-process-newsgroups
(list
(list "^nntp+news.gmane.org" 'gnus-group-spam-exit-processor-report-gmane)
))
and then entered a gmane group, marked the spam articles with M-d, and
exited the group. The minibuffer messages were
Marking spam as expired without moving it
Exiting summary buffer and applying spam rules
How do I know if the setting of gnus-spam-process-newsgroups "took"?
I don't think it did, because the exit was too fast.
It wasn't held up by doing 6 HTTP requests to gmane.
Thanx!
- Steinar
next prev parent reply other threads:[~2003-09-27 22:39 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-25 19:12 Steinar Bang
2003-09-25 19:52 ` Reiner Steib
2003-09-27 22:45 ` Steinar Bang
2003-09-27 23:02 ` Steinar Bang
2003-09-28 13:46 ` Reiner Steib
2003-10-02 18:40 ` Ted Zlatanov
2003-10-02 20:00 ` Reiner Steib
2003-09-25 20:27 ` Ted Stern
2003-09-27 22:39 ` Steinar Bang [this message]
2003-09-27 23:08 ` Steinar Bang
2003-10-02 18:31 ` 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=87d6dl6els.fsf@doohan.bang.priv.no \
--to=sb@dod.no \
/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).