Gnus development mailing list
 help / color / mirror / Atom feed
From: Ted Zlatanov <tzz@lifelogs.com>
Subject: Re: How to load spam.el just for gmane reporting?
Date: Thu, 02 Oct 2003 14:31:18 -0400	[thread overview]
Message-ID: <4nvfr77aq1.fsf@lockgroove.bwh.harvard.edu> (raw)
In-Reply-To: <87d6dl6els.fsf@doohan.bang.priv.no> (Steinar Bang's message of "Sun, 28 Sep 2003 00:39:11 +0200")

On Sun, 28 Sep 2003, sb@dod.no wrote:

>>>>>> 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?

spam-use-* is necessary for any normal use of spam.el.  What you're
doing, loading it just for the spam exit processor (gmane reporting in
this case) is not wrong, but I would probably isolate the commentary
to the as-of-yet-unwritten spam-report.el documentation :)

You do have to set spam-install-hooks if you don't have any of the
spam-use-* variables set.

> 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. 

You can also do it by regular expressions I believe (see
gnus-spam-process-newsgroups).

> So I guess I'll have to figure out how to set up the
> gnus-spam-process-destinations variable.

gnus-spam-process-destinations only applies to where processed spam
will go after processing (it will be moved), probably not what you
want in a gmane group.  I would leave it nil for gmane groups.

> 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.

Increase gnus-verbose and you should see the messages about reporting
spam to gmane.

HTH
Ted



      parent reply	other threads:[~2003-10-02 18:31 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
2003-09-27 23:08     ` Steinar Bang
2003-10-02 18:31     ` Ted Zlatanov [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=4nvfr77aq1.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).