From: Ted Zlatanov <tzz@lifelogs.com>
Subject: Re: Some spam messages are not sorted into the corresponding group
Date: Tue, 04 Feb 2003 16:26:15 -0500 [thread overview]
Message-ID: <4n1y2ng2ko.fsf@lockgroove.bwh.harvard.edu> (raw)
In-Reply-To: <87smv3daw5.fsf@splinter.inka.de> (Christopher Splinter's message of "Tue, 04 Feb 2003 21:54:50 +0100")
On Tue, 04 Feb 2003, chris@splinter.inka.de wrote:
> (spam-split) used in *Article* (on the full message, of course),
> returns "junk", which is the value of spam-split-group. In spite
> of that, the mail's not split properly.
>
>> Could something else in your split methods be matching?
>
> I wouldn't think so, there's only one entry which moves
> messages to mail.misc:
>
> (setq nnmail-split-fancy
> '(| (: spam-split)
> [...]
> "mail.misc"))
>
> If that's not enough, I can post the rest of the list too; it
> wouldn't be very enlightening, though.
I'm pretty stumped. spam-split is behaving exactly as it should by
itself; spam-check-bogofilter is behaving exactly as it should by
itself. Inside nnmail-split-fancy, however, they fail.
How about
(defun spam-split-test ()
(debug (spam-split))
nil)
Add (: spam-split-test) in your nnmail-split-fancy before spam-split
and see what the debug error is. Hit `c' to continue once you hit the
debugger. Let me know what the stack trace says - it will tell us
what really is happening in there.
Thanks
Ted
next prev parent reply other threads:[~2003-02-04 21:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-01 9:27 Christopher Splinter
2003-02-01 20:24 ` Ted Zlatanov
2003-02-02 8:33 ` Christopher Splinter
2003-02-04 19:15 ` Ted Zlatanov
2003-02-04 20:54 ` Christopher Splinter
2003-02-04 21:26 ` Ted Zlatanov [this message]
2003-02-05 12:33 ` Christopher Splinter
2003-02-05 19:09 ` 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=4n1y2ng2ko.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).