From: Robert Raschke <rrplan9@tombob.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] question on mail/setup.bayes and existing pipeto
Date: Tue, 25 Apr 2006 15:11:54 +0100 [thread overview]
Message-ID: <27d6e365c210506165ccd3d21a91875f@tombob.com> (raw)
In-Reply-To: <d6de644da8ff9dc6146e148656f59722@tombob.com>
I wrote around Mon Apr 24 14:38:36 BST 2006:
> I want to start using the bayes filtering for spam. I also have a
> pipeto for splitting apart my incoming mail stream according to
> mailing list (and such) like this: [...snip...]
I think I've figured out how to do this. After I ran setup.bayes, I
had a new pipeto and my old one in pipeto.0. By changing my standard
bayes pipeto from
[...snip...]
if(isspam)
spool-tagged-spam
if not
spool /mail/box/$USER/mbox
exit 0
to
[...snip...]
if(isspam)
spool-tagged-spam
if not
pipe /mail/box/$USER/pipeto.0 $*
exit 0
I get my old behaviour back.
Robby
prev parent reply other threads:[~2006-04-25 14:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-24 13:37 Robert Raschke
2006-04-25 14:11 ` Robert Raschke [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=27d6e365c210506165ccd3d21a91875f@tombob.com \
--to=rrplan9@tombob.com \
--cc=9fans@cse.psu.edu \
/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).