From: kai.grossjohann@gmx.net (Kai Großjohann)
Subject: Re: Incorporating old mail issues
Date: Mon, 18 Aug 2003 18:23:57 +0200 [thread overview]
Message-ID: <84d6f3c4te.fsf@slowfox.is.informatik.uni-duisburg.de> (raw)
In-Reply-To: <874r0ir3qx.fsf@wozniak.ca>
Geoff Wozniak <geoff@wozniak.ca> writes:
> However, I've hit a snag. I have about a year's worth of mail that was
> originally stored using VM. When I add these files to the group list using
> `gnus-group-make-doc-group' (G f) and then enter that group, the group will
> have significantly less messages than are actually in the file. Normally,
> it reports only 3 messages.
Whee. How could it happen? Hm. Since I don't see the actual file,
I can only guess.
Is the first message a multipart/*? That might cause it to gobble
the next messages, if you're unfortunate. Not that I've ever seen
this effect, though.
Is every From_ line (except for the first) preceded by an empty line?
It must be, for Gnus to grok the file.
Do some messages have bogus Content-Length headers?
--
Two cafe au lait please, but without milk.
prev parent reply other threads:[~2003-08-18 16:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-15 21:48 Geoff Wozniak
2003-08-18 16:23 ` Kai Großjohann [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=84d6f3c4te.fsf@slowfox.is.informatik.uni-duisburg.de \
--to=kai.grossjohann@gmx.net \
/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).