all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: Skip Montanaro <skip.montanaro@gmail.com>
Cc: Help GNU Emacs <help-gnu-emacs@gnu.org>
Subject: Re: Read/process mbox file in Gnus
Date: Thu, 05 Nov 2020 17:45:23 -0800	[thread overview]
Message-ID: <87blgb8dho.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <CANc-5UxSDjQFhJMbmOjh9xJeCABf-JwUXi6yGer1zZjUV-AThQ@mail.gmail.com> (Skip Montanaro's message of "Thu, 5 Nov 2020 10:58:44 -0600")

Skip Montanaro <skip.montanaro@gmail.com> writes:

> I recently switched to Manjaro from Ubuntu and decided to (finally) give
> Gnus a try (VM no longer seems to be actively maintained and I'd prefer not
> to install it from source different than everything else - which comes via
> elpa/melpa). Up 'til now, I've used VM to do the mail processing for my
> spam work related to mail.python.org. The workflow goes something like this:
>
>    1. Assemble an mbox file of unsure messages on mail.python.org (mpo)
>    2. Download it to my laptop
>    3. Process it, saving some messages as spam, others as ham, and
>    discarding the rest
>    4. Upload the new spam and ham mbox files to mpo
>    5. Retrain the system with the new messages
>
> I have been using VM for step three. I'd like to do that with Gnus. Looking
> through the manual, skimming Google search output and skimming an apropos
> list of gnus commands I didn't see an obvious way to read a Unix mbox file.
> I'm sure I must be missing something basic. Pointers appreciated.

The easiest thing to do will be to follow the workflow here:

(gnus) Incorporating Old Mail

That requires you to manually mark and respool all the messages in the
resulting group, but maybe that's actually what you want -- to
explicitly deal with each message.

I'd be curious to know if Gnus+tramp can handle a remote filename
transparently here -- you might be able to skip step 2.

The only other solution that I would consider "normal" here is to have
the message dump (whether remote or local) set up as a "mail source" in
Gnus ("Mail Sources" in the manual). Gnus then knows that it should
regularly check that source for new messages to fetch. You could either
use mail splitting to do a bit of automatic pre-processing, or just
specify that all incoming messages should go to a single group.

mbox doesn't seem to be one of the supported mail source formats,
though. maildir is, and I also wonder if the "directory" specifier might
work. Maybe you can stick the mbox file in a particular directory, then
set the directory specifier's :path keyword to that directory, and the
:suffix keyword to ".mbox".

Someone else might have tried this before?

HTH,
Eric



  reply	other threads:[~2020-11-06  1:45 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-05 16:58 Read/process mbox file in Gnus Skip Montanaro
2020-11-06  1:45 ` Eric Abrahamsen [this message]
2020-11-06 10:44   ` Robert Pluim
2020-11-06 12:19     ` Eric S Fraga
2020-11-06 13:09       ` Skip Montanaro
2020-11-06 13:27         ` Eric S Fraga
2020-11-06 16:27           ` Eric Abrahamsen
2020-11-06 18:40         ` Skip Montanaro
2020-11-09 13:40           ` Eric S Fraga
2020-11-06 15:34     ` Colin Baxter
2020-11-06 16:22       ` Robert Pluim
2020-11-06 18:03         ` Colin Baxter

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=87blgb8dho.fsf@ericabrahamsen.net \
    --to=eric@ericabrahamsen.net \
    --cc=help-gnu-emacs@gnu.org \
    --cc=skip.montanaro@gmail.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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.