From: Reiner Steib <reinersteib+gmane@imap.cc>
To: Ronan Keryell <Ronan.Keryell@hpc-project.com>
Cc: ding@gnus.org, bugs@gnus.org
Subject: Re: Loosing mails by merging
Date: Wed, 25 Nov 2009 23:01:17 +0100 [thread overview]
Message-ID: <87iqcyb6xe.fsf@marauder.physik.uni-ulm.de> (raw)
In-Reply-To: <877htfdd7g.fsf@an-dro.enstb.org> (Ronan Keryell's message of "Tue, 24 Nov 2009 18:50:27 +0100")
On Tue, Nov 24 2009, Ronan Keryell wrote:
>>>>>> Reiner Steib <reinersteib+gmane@imap.cc> said:
>
> Reiner> You're talking about doing something like `G f GNUS-bug.mbox
> Reiner> RET' (gnus-group-make-doc-group), right?
>
> Not only.
>
> Reiner> Use `C-u G f m GNUS-bug.mbox RET' instead.
>
> Reiner> When catting your sample file to $MAIL, I get the expected
> Reiner> result.
>
> Yes, with this I can read my mail correctly as a mbox format.
>
> So the good news is that GNUS can do it. :-)
>
> The bad news is that means that G f does not guess the good format.
That's a known problem because it not possible to do it correct in any
case, IIRC.
> The very bad news for me is that I have this issue on my normal mail,
> not only file group.
If you cat your sample file to $MAIL, say ...
cat GNUS-bug.mbox >> /var/mail/you
... do you get 2 messages or 1 after `g'?
I get 2 as expected.
> I get my mail with some:
> (setq mail-sources '(
> ;; Pick mail in the local mail repository,
> ;; if mail is lost here or droped by other means...
> (file)
Try with a simple setup like ...
(setq mail-sources '((file)))
... first.
> ;; get some remote mail in the local mail repository:
> (file :prescript "fdm -l -v fetch")
> ;; Pick mail in the central mail repository:
> (file :prescript "ssh info bin/recup_mail --fetch >%t"
> :postscript "ssh info bin/recup_mail --archive")
> ))
>
> So basically almost everything lands into my /var/mail/keryell and is
> digested by Gnus. But then this bug means that it is not read with the
> correct mbox format?
>
> I've read again the "Mail Source Specifiers" section and around of the
> manual and there is no way to enforce the format as being a mbox one...
It should work by default.
Bye, Reiner.
--
,,,
(o o)
---ooO-(_)-Ooo--- | PGP key available | http://rsteib.home.pages.de/
prev parent reply other threads:[~2009-11-25 22:01 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
2009-11-24 17:50 ` Ronan Keryell
2009-11-25 22:01 ` Reiner Steib [this message]
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=87iqcyb6xe.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).