From: Reiner Steib <reinersteib+gmane@imap.cc>
To: ding@gnus.org, Ronan Keryell <Ronan.Keryell@hpc-project.com>
Cc: bugs@gnus.org
Subject: Re: Loosing mails by merging
Date: Sat, 21 Nov 2009 20:38:30 +0100 [thread overview]
Message-ID: <87d43bk6rt.fsf@marauder.physik.uni-ulm.de> (raw)
In-Reply-To: <87ocmyrw3a.fsf@an-dro.enstb.org> (Ronan Keryell's message of "Thu, 19 Nov 2009 23:25:13 +0100")
On Thu, Nov 19 2009, Ronan Keryell wrote:
> Gnus v5.13
> GNU Emacs 23.1.1 (x86_64-pc-linux-gnu, GTK+ Version 2.18.3)
> of 2009-11-02 on excelsior, modified by Debian
> 200 news.gmane.org InterNetNews NNRP server INN 2.4.1 ready (posting ok).
>
> I guess I regularly loose some mails because of a wrong parsing of my
> mbox file that make them to be merged in a previous SPAM for example. :-(
>
> I've put an example with the 2 first mails of my GNUS mbox backup file
> ~/Mail/Incoming4562Z0v in http://enstb.org/~keryell/GNUS-bug.mbox
>
> The summary buffer displays:
> . [ 221: Zapadlo ] <* mixed> XXXX
> . [ 32: Zapadlo ] <1 text>
> . [ 51: Zapadlo ] <2 rfc822>
> . [ 29: Zapadlo ] <2 text> XXXX
>
> What we should have instead is something like that:
> Zapadlo XXXX
> Otis Saunders Wang up!
You're talking about doing something like `G f GNUS-bug.mbox RET'
(gnus-group-make-doc-group), right?
Use `C-u G f m GNUS-bug.mbox RET' instead.
When catting your sample file to $MAIL, I get the expected result.
> In the full mbox file, it makes me 185 mails to disappear. :-(
>
> Any idea how to eradicate this mixing up?
Bye, Reiner.
--
,,,
(o o)
---ooO-(_)-Ooo--- | PGP key available | http://rsteib.home.pages.de/
next parent reply other threads:[~2009-11-21 19:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87ocmyrw3a.fsf@an-dro.enstb.org>
2009-11-21 19:38 ` Reiner Steib [this message]
2009-11-24 17:50 ` Ronan Keryell
2009-11-25 22:01 ` Reiner Steib
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=87d43bk6rt.fsf@marauder.physik.uni-ulm.de \
--to=reinersteib+gmane@imap.cc \
--cc=Reiner.Steib@gmx.de \
--cc=Ronan.Keryell@hpc-project.com \
--cc=bugs@gnus.org \
--cc=ding@gnus.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).