Gnus development mailing list
 help / color / mirror / Atom feed
From: Ted Zlatanov <tzz@lifelogs.com>
Cc: ding@gnus.org
Subject: Re: Trouble with spam.el and ifile
Date: Tue, 07 Jan 2003 23:55:35 -0500	[thread overview]
Message-ID: <m37kdgme9k.fsf@heechee.beld.net> (raw)
In-Reply-To: <y68smw460qd.fsf@multics.mit.edu> (David Z Maze's message of "Tue, 07 Jan 2003 17:42:18 -0500")

On Tue, 07 Jan 2003, dmaze@MIT.EDU wrote:
> -- 'unless' isn't the opposite of 'if' (it's the opposite of 'when',
> though).  `spam-check-ifile' now unconditionally sets the group name
> to what gets returned from ifile, regardless of the setting of
> spam-ifile-all-categories, which is wrong.  You really want the (if
> (not spam-ifile-all-categories) ...) form my original patch had.

I see what I did, I missed the else part of the if - I thought it was
just the 'if'.  Oops.

> -- 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 the way, I think that if you set the spam group's contents to spam,
it will override a global regex of ham for "nnml.*" - have you tried
that?

Ted




  reply	other threads:[~2003-01-08  4:55 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 [this message]
2003-01-08 15:11         ` Ted Zlatanov
2003-01-08 16:07           ` David Z Maze
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=m37kdgme9k.fsf@heechee.beld.net \
    --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).