Gnus development mailing list
 help / color / mirror / Atom feed
From: Ted Zlatanov <tzz@lifelogs.com>
Cc: ding@gnus.org
Subject: Re: How many people mark spam in gmane groups?
Date: Tue, 29 Apr 2003 14:04:20 -0400	[thread overview]
Message-ID: <4nr87lqixn.fsf@lockgroove.bwh.harvard.edu> (raw)
In-Reply-To: <87wuhddwjl.fsf@jpl.nasa.gov> (Jon Ericson's message of "Tue, 29 Apr 2003 10:48:46 -0700")

On Tue, 29 Apr 2003, Jon.Ericson@jpl.nasa.gov wrote:
> I am using spam.el, but spam-report-gmane-regex doesn't work for me.
> If I understand the code, I don't see how it could be useful.  The
> only place it's used is in spam-report-gmane, but that's only called
> by spam-summary-prepare-exit if the gnus-group-spam-exit-processor-
> report-gmane group parameter is set.  It seems like the check
> against the regexp should be in spam.el and not in spam-report.el.
> Or am I missing something?

spam-report-gmane-regex is consulted only when spam-report-gmane is
invoked.  To invoke it, you have to activate the
gnus-group-spam-exit-processor-report-gmane spam exit processor.
Customize the variable gnus-spam-process-newsgroups (you could also do
it with group/topic parameters but you already said you can't).

> (I hope I don't come off as sarcastic; I really do appreciate the
> bits of spam.el that I'm now using.  The only thing preventing me
> from using more features is inertia.)

Not at all, I appreciate feedback and suggestions.  I know spam.el is
a bit intimidating to new users, and will try to put some useful
novice info in the manual in time for Gnus 5.10.

Thanks
Ted



  reply	other threads:[~2003-04-29 18:04 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-02 15:59 Ted Stern
2003-04-02 16:54 ` Reiner Steib
2003-04-02 20:58   ` Jon Ericson
2003-04-05 13:20   ` Ted Zlatanov
2003-04-05 23:16     ` Reiner Steib
2003-04-07 20:49       ` Ted Zlatanov
2003-04-12 15:50         ` Andreas Fuchs
2003-04-12 20:58           ` Lars Magne Ingebrigtsen
2003-04-13 10:56             ` Andreas Fuchs
2003-04-13 13:31               ` Lars Magne Ingebrigtsen
2003-04-14 19:33               ` Ted Zlatanov
2003-04-14 21:03                 ` Andreas Fuchs
2003-04-14 21:05                 ` Reiner Steib
2003-04-14 23:32                   ` Ted Zlatanov
2003-04-15 14:24                     ` Reiner Steib
2003-04-15  5:34                   ` Steinar Bang
2003-04-15 14:23                     ` Reiner Steib
2003-04-15 19:33                     ` Ted Zlatanov
2003-04-15 21:42                       ` Andreas Fuchs
2003-04-15 22:31                         ` Lars Magne Ingebrigtsen
2003-04-16  6:02                           ` Andreas Fuchs
2003-04-16 16:33         ` Ted Zlatanov
2003-04-26  1:40           ` Jon Ericson
2003-04-29 17:19             ` Ted Zlatanov
2003-04-29 17:48               ` Jon Ericson
2003-04-29 18:04                 ` Ted Zlatanov [this message]
2003-04-29 19:48                   ` Jon Ericson
2003-04-30 18:28                     ` Ted Zlatanov
2003-04-30 21:37                       ` Jon Ericson
2003-05-01 17:34                         ` Ted Zlatanov
2003-04-26  2:49           ` Jon Ericson
2003-04-27  3:41             ` Lars Magne Ingebrigtsen
2003-04-28 18:36               ` Jon Ericson
2003-04-29 17:12                 ` Ted Zlatanov
2003-04-30 18:37                   ` Jon Ericson
2003-04-02 19:32 ` Raja R Harinath
2003-04-13  1:31   ` Daniel Néri

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=4nr87lqixn.fsf@lockgroove.bwh.harvard.edu \
    --to=tzz@lifelogs.com \
    --cc=ding@gnus.org \
    /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).