From: wgreenhouse-sGOZH3hwPm2sTnJN9+BGXg@public.gmane.org (W. Greenhouse)
To: help-gnu-emacs-mXXj517/zsQ@public.gmane.org
Subject: Re: What are advantages and disadvantages of RMAIL and mh-rmail ?
Date: Sat, 28 Sep 2013 06:17:21 +0000 [thread overview]
Message-ID: <87d2nt1nda.fsf@motoko.kusanagi> (raw)
In-Reply-To: 87had5604d.fsf@nl106-137-194.student.uu.se
Emanuel Berg <embe8573-oe7qfRrRQfc4M/bo5TPICw@public.gmane.org> writes:
[...]
> mbox gets the best result, and it makes sense (no
> threading the same mail etc.), *but* it goes on only for
> 30 messages (that are all very recent). Perhaps some
> message isn't sound, and it works from the present, and
> back, and it gets stuck on that?
Sounds like a likely guess. I would cross-check with RMAIL to see what
that 31st message is, and perhaps quarantine it temporarily, moving it
to another file to see if you can continue.
--
Regards,
WGG
next prev parent reply other threads:[~2013-09-28 6:17 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-18 11:07 What are advantages and disadvantages of RMAIL and mh-rmail ? Don Saklad
2013-08-21 16:12 ` W. Greenhouse
[not found] ` <mailman.503.1377101598.10748.help-gnu-emacs@gnu.org>
2013-09-22 15:49 ` Emanuel Berg
2013-09-22 20:33 ` William G. Gardella
[not found] ` <mailman.2713.1379882719.10748.help-gnu-emacs@gnu.org>
2013-09-23 22:13 ` Emanuel Berg
2013-09-24 3:03 ` Emanuel Berg
2013-09-24 6:38 ` Glyn Millington
2013-09-24 19:37 ` James Freer
2013-09-24 6:38 ` Tassilo Horn
[not found] ` <mailman.2779.1380004725.10748.help-gnu-emacs@gnu.org>
2013-09-24 19:01 ` Emanuel Berg
2013-09-28 0:26 ` Emanuel Berg
2013-09-28 2:12 ` W. Greenhouse
[not found] ` <mailman.3038.1380334353.10748.help-gnu-emacs@gnu.org>
2013-09-28 3:17 ` Emanuel Berg
2013-09-28 3:54 ` W. Greenhouse
[not found] ` <mailman.3041.1380340468.10748.help-gnu-emacs@gnu.org>
2013-09-28 4:27 ` Emanuel Berg
2013-09-28 6:17 ` W. Greenhouse [this message]
[not found] ` <mailman.3043.1380349067.10748.help-gnu-emacs@gnu.org>
2013-09-28 8:59 ` Emanuel Berg
2013-09-28 9:26 ` Eli Zaretskii
[not found] ` <mailman.3059.1380360406.10748.help-gnu-emacs@gnu.org>
2013-09-28 9:40 ` Emanuel Berg
2013-09-28 11:14 ` Eli Zaretskii
[not found] ` <mailman.3065.1380366869.10748.help-gnu-emacs@gnu.org>
2013-09-28 11:38 ` Emanuel Berg
2013-09-28 14:25 ` Eli Zaretskii
[not found] ` <mailman.3075.1380378319.10748.help-gnu-emacs@gnu.org>
2013-09-28 18:00 ` Emanuel Berg
2013-09-28 18:46 ` Eli Zaretskii
[not found] ` <mailman.3098.1380393985.10748.help-gnu-emacs@gnu.org>
2013-09-28 19:14 ` Emanuel Berg
2013-09-28 20:42 ` Eli Zaretskii
2013-09-28 14:41 ` Dale Snell
[not found] ` <mailman.3076.1380379289.10748.help-gnu-emacs@gnu.org>
2013-09-28 18:01 ` Emanuel Berg
2013-09-28 15:28 ` W. Greenhouse
[not found] ` <mailman.3079.1380382129.10748.help-gnu-emacs@gnu.org>
2013-09-28 18:09 ` Emanuel Berg
[not found] ` <mailman.2780.1380006069.10748.help-gnu-emacs@gnu.org>
2013-09-24 19:05 ` Emanuel Berg
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=87d2nt1nda.fsf@motoko.kusanagi \
--to=wgreenhouse-sgozh3hwpm2stnjn9+bgxg@public.gmane.org \
--cc=help-gnu-emacs-mXXj517/zsQ@public.gmane.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 read-only IMAP folder(s) and NNTP newsgroup(s).