Gnus development mailing list
 help / color / mirror / Atom feed
From: Reiner Steib <reinersteib+gmane@imap.cc>
Cc: emacs-pretest-bug@gnu.org, ding@gnus.org
Subject: Re: Gnus MIME parsing bug?
Date: Sat, 06 May 2006 21:59:48 +0200	[thread overview]
Message-ID: <v9r736zzyj.fsf@marauder.physik.uni-ulm.de> (raw)
In-Reply-To: <200605060247.k462lWHR091088@gothmog.pc> (Giorgos Keramidas's message of "Sat, 6 May 2006 05:47:32 +0300 (EEST)")

[ CC-ing ding@gnus ]

On Sat, May 06 2006, Giorgos Keramidas wrote:

> I have a UNIX mailbox with several MIME messages with multiple
> alternative parts, which comes up with seven different messages when
> opened in Mutt:
>
>    1 r + 2006-02-26 Petros V             (   67) about svn
>    2 r + 2006-02-28 Petros V             (   90) `->
>    3 r + 2006-03-02 Petros V             (   53)   `->
>    4 r + 2006-03-04 Petros V             (   91)     `->
>    5 r + 2006-03-06 Petros V             (   47)       `->
>    6 r + 2006-04-28 Petros V             (   76)         `->
>    7   + 2006-04-29 Petros V             (  328)           `->
>
> Then I create an nndoc group and try to import messages from this
> mailbox though, Gnus shows only 3 messages.  It looks like some of the
> messages are 'eaten' by the part that splits the mailbox in separate
> mail messages.  This only seems to happen with messages that have
> multiple alternative parts (i.e. text/plain and text/html).

Did you try to specify mbox explicitely instead of letting Gnus guess
the type of the file?  I.e. `C-u G f file RET m'?

> In GNU Emacs 22.0.50.1 (i386-unknown-freebsd7.0, GTK+ Version 2.8.17)
>  of 2006-05-06 on gothmog.pc

Bye, Reiner.
-- 
       ,,,
      (o o)
---ooO-(_)-Ooo---  |  PGP key available  |  http://rsteib.home.pages.de/

       reply	other threads:[~2006-05-06 19:59 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200605060247.k462lWHR091088@gothmog.pc>
2006-05-06 19:59 ` Reiner Steib [this message]
2006-05-07 14:39   ` Giorgos Keramidas

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=v9r736zzyj.fsf@marauder.physik.uni-ulm.de \
    --to=reinersteib+gmane@imap.cc \
    --cc=Reiner.Steib@gmx.de \
    --cc=ding@gnus.org \
    --cc=emacs-pretest-bug@gnu.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).