Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: Reiner Steib <reinersteib+from-uce@imap.cc>
Subject: Re: bug in reading outlook multipart email?
Date: Sun, 13 Feb 2005 15:25:08 +0100	[thread overview]
Message-ID: <v9oeeobkqj.fsf@marauder.physik.uni-ulm.de> (raw)
In-Reply-To: <1108232322.995783.258720@o13g2000cwo.googlegroups.com>

On Sat, Feb 12 2005, Pedro Kroger wrote:

> I started tracking the problem down and it seems that the culprit is
> multipart email sent by Microsoft Outlook Express 6.00 (or something
> like that). It seems that gnus can't see others emails beyond that
> point.
>
> Here is an example. This mbox file:
>
> http://www.pedrokroeger.net/gnus/bug-gnus
>
> has 2 messagens, as can be seen here in mutt:
>
> http://www.pedrokroeger.net/gnus/mutt-summary.png

[ I didn't look at this because I'm offline. ]

> But if I try to see this file in gnus using nndoc, I can see only one
> message and it's parts: [...]

Concerning nndoc: Did you try the prefix argument of
`gnus-group-make-doc-group' (C-u G f)?

,----[ (info "(gnus)Foreign Groups") ]
| `G f'
|      Make a group based on some file or other
|      (`gnus-group-make-doc-group').  If you give a prefix to this
|      command, you will be prompted for a file name and a file type.
|      Currently supported types are `mbox', `babyl', `digest', `news',
|      `rnews', `mmdf', `forward', `rfc934', `rfc822-forward',
|      `mime-parts', `standard-digest', `slack-digest', `clari-briefs',
|      `nsmail', `outlook', `oe-dbx', and `mailman'.  If you run this
|      command without a prefix, Gnus will guess at the file type.  *Note
|      Document Groups::.
`----

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


      reply	other threads:[~2005-02-13 14:25 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-12 18:18 Pedro Kroger
2005-02-13 14:25 ` 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=v9oeeobkqj.fsf@marauder.physik.uni-ulm.de \
    --to=reinersteib+from-uce@imap.cc \
    --cc=Reiner.Steib@gmx.de \
    /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).