Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: Geoff Kuenning <geoff@cs.hmc.edu>
To: info-gnus-english@gnu.org
Subject: Modifiable mbox?
Date: 10 Apr 2007 01:19:26 -0700	[thread overview]
Message-ID: <pniirc463qp.fsf_-_@bow.cs.hmc.edu> (raw)

I procmail presumed spam into an mbox file, and then periodically scan
it for ham.  Right now, I use rmail to move the ham elsewhere and
delete it from the mbox; then I convert it from Babyl back to mbox and
feed it to spamassassin for Bayesian learning.

The problem with that method is that rmail isn't my favorite
interface, and in fact it breaks after 10,000 messages.  I'd prefer to
use gnus to do my filtering and processing.  The problem is that I
can't figure out how to make gnus descend into an mbox in a writeable
fashion.  gnus-group-make-doc-group is great for browsing the group,
but doesn't let me delete ham after I've written it to a different file.

Is it possible to get gnus to descend into an mbox without
reformatting it into nnml, but still being able to delete messages?
I'd rather not move thousands of messages into separate files, since
then I'd just have to collect everything together again to feed it to
Spamassassin.

I'm also open to alternative suggestions.  My requirements are that I
need to save semi-spam in a procmail-friendly way, use gnus to move
the few real ham messages to a different place, and easily feed the
remaining stuff to spamassassin.  Other than that, I'm willing to
change how I do things.
-- 
    Geoff Kuenning   geoff@cs.hmc.edu   http://www.cs.hmc.edu/~geoff/

If you can't measure it, it's not science.
	-- Robert A. Heinlein, "The Door Into Summer"

             reply	other threads:[~2007-04-10  8:19 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-10  8:19 Geoff Kuenning [this message]
2007-04-11 14:07 ` Kai Grossjohann
2008-01-08 10:55 ` Image-display troubles Geoff Kuenning
2008-01-08 23:55   ` Katsumi Yamaoka
2008-01-09  1:52     ` Geoff Kuenning
2008-01-09 23:36   ` Geoff Kuenning

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=pniirc463qp.fsf_-_@bow.cs.hmc.edu \
    --to=geoff@cs.hmc.edu \
    --cc=info-gnus-english@gnu.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).