From: Oystein Viggen <oysteivi@tihlde.org>
Subject: Re: Splitting on mail contents? (using spam-stat.el)
Date: Wed, 04 Sep 2002 19:00:18 +0200 [thread overview]
Message-ID: <03k7m1lmfx.fsf@msgid.viggen.net> (raw)
In-Reply-To: <uv6r8g9n5id.fsf@suspiria.ai.mit.edu>
* [Jeremy H. Brown]
> This works with 5.8.8/5.9; I have no idea how it does with oort.
This seems to work in Oort, too. Thanks a lot!
Oystein
--
When in doubt: Recompile.
next prev parent reply other threads:[~2002-09-04 17:00 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-04 12:01 Oystein Viggen
2002-09-04 14:00 ` Kai Großjohann
2002-09-04 14:16 ` Oystein Viggen
2002-09-04 14:56 ` Kai Großjohann
2002-09-04 15:16 ` Oystein Viggen
2002-09-04 15:23 ` Jeremy H. Brown
2002-09-04 17:00 ` Oystein Viggen [this message]
2002-09-13 16:18 ` finding the article buffer when splitting Alex Schroeder
2002-09-13 23:56 ` Oystein Viggen
2002-09-14 1:18 ` Alex Schroeder
2002-09-14 10:01 ` Oystein Viggen
2002-09-15 18:21 ` Jeremy H. Brown
2002-09-23 14:11 ` Alex Schroeder
2002-09-23 18:49 ` Oystein Viggen
2002-09-06 15:55 ` Splitting on mail contents? (using spam-stat.el) Alex Schroeder
2002-09-07 12:30 ` Alex Schroeder
2002-09-07 17:17 ` Simon Josefsson
2002-09-07 19:05 ` Kai Großjohann
2002-09-07 19:05 ` Kai Großjohann
2002-09-12 16:07 ` Paul Jarc
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=03k7m1lmfx.fsf@msgid.viggen.net \
--to=oysteivi@tihlde.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).