unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Robert Pluim <rpluim@gmail.com>
To: Eric Abrahamsen <eric@ericabrahamsen.net>
Cc: Skip Montanaro <skip.montanaro@gmail.com>,
	Help GNU Emacs <help-gnu-emacs@gnu.org>
Subject: Re: Read/process mbox file in Gnus
Date: Fri, 06 Nov 2020 11:44:17 +0100	[thread overview]
Message-ID: <87h7q2ix32.fsf@gmail.com> (raw)
In-Reply-To: <87blgb8dho.fsf@ericabrahamsen.net> (Eric Abrahamsen's message of "Thu, 05 Nov 2020 17:45:23 -0800")

Eric Abrahamsen <eric@ericabrahamsen.net> writes:

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

>> 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.
>

'G f' (gnus-group-make-doc-group) will happily create a Gnus group
from an mbox file

> 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".

Iʼm told that Gnus' maildir support is not great (Iʼve never tried it
myself)

Robert



  reply	other threads:[~2020-11-06 10:44 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
2020-11-06 10:44   ` Robert Pluim [this message]
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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87h7q2ix32.fsf@gmail.com \
    --to=rpluim@gmail.com \
    --cc=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.
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 read-only IMAP folder(s) and NNTP newsgroup(s).