From: Adam Duck <duck@informatik.uni-frankfurt.de>
Subject: Re: spam-split doesn't split
Date: Sat, 13 Dec 2003 11:29:17 +0100 [thread overview]
Message-ID: <86isklnh8i.fsf@oumu.wohnheimb.uni-frankfurt.de> (raw)
In-Reply-To: <4nfzfp8ztw.fsf@collins.bwh.harvard.edu>
Ted Zlatanov <tzz@lifelogs.com> writes:
> On Fri, 12 Dec 2003, duck@informatik.uni-frankfurt.de wrote:
>
>> I have to say that I'm already using gnus-cvs and emacs-cvs (it's in
>> portage on gentoo). Still, `spam-split' is not moving spam.
>
> Try increasing gnus-verbose to 10 and see what is in the *Messages*
> buffer.
Well well, I've got it now. Seems the group name "bogus" is used if
something goes wrong. Anyway, the problem was this:
`nnmail-split-fancy' is a variable declared in Lisp.
-- loaded from "nnmail"
Value: (:spam-split)
Why didn't anybody tell me I have a space missing? "(: spam-split)"
works just fine. How could I have ever doubt gnus programmers? :)
> Finally, Xavier brought up a good point - is gentoo's portage a few
> steps behind CVS or is it the latest CVS? I've never used portage.
Well, gentoo's pretty cool in this regard. It synchs cvs-trees here on
my box, copies them to a working directory and builds the
package. gentoo builds everything from source. So, when *I* do an
"emerge gnus-cvs" I get the latest. Anyway, I don't know if the patch
helped.
thanks, Adam.
next prev parent reply other threads:[~2003-12-13 10:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-09 18:07 Adam Duck
2003-12-09 22:29 ` Ted Zlatanov
2003-12-11 16:16 ` Adam Duck
2003-12-11 19:15 ` Ted Zlatanov
2003-12-11 23:35 ` Adam Duck
2003-12-12 18:28 ` Xavier Maillard
2003-12-12 21:56 ` Ted Zlatanov
2003-12-13 10:29 ` Adam Duck [this message]
2003-12-13 17:54 ` Xavier Maillard
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=86isklnh8i.fsf@oumu.wohnheimb.uni-frankfurt.de \
--to=duck@informatik.uni-frankfurt.de \
/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).