Gnus development mailing list
 help / color / mirror / Atom feed
From: Kai.Grossjohann@CS.Uni-Dortmund.DE
Subject: Re: More POP madness
Date: 09 Apr 1999 15:34:02 +0200	[thread overview]
Message-ID: <vafpv5dlxyt.fsf@ramses.cs.uni-dortmund.de> (raw)
In-Reply-To: Chris Tessone's message of "08 Apr 1999 14:28:46 -0500"

Chris Tessone <tessone@imsa.edu> writes:

  > Secondly, how can I retrieve the mail from the Incoming file if Gnus
  > *does* lose it? Making a new nndoc group didn't work --- it kept
  > giving me an error when I tried to open the new group.

If you can't `G f' the Incoming file, then the file is broken.  Have a
look at it (with C-x C-f) and see if you can salvage stuff.

Gnus should warn you, though.  But we don't know what's wrong with
that file, yet, so maybe it will help if you tell us what it looks
like and where you think the problem is.  (You might be able to find
the problem by splitting the file into two then using `G f' on both
files, and so on until you find the problem.)

kai
-- 
Abort this operation?   [Abort]  [Cancel]


  parent reply	other threads:[~1999-04-09 13:34 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-04-08 19:28 Chris Tessone
1999-04-08 22:01 ` Alexandre Oliva
1999-04-08 23:15   ` Chris Tessone
1999-04-08 23:18     ` Chris Tessone
1999-04-08 23:36       ` Stainless Steel Rat
1999-04-09  0:04         ` Chris Tessone
1999-04-10  0:19           ` Stainless Steel Rat
1999-04-10 22:24             ` Kai.Grossjohann
1999-04-11 13:45               ` Stainless Steel Rat
1999-04-09  6:31 ` Dmitry Yaitskov
1999-04-09 13:34 ` Kai.Grossjohann [this message]
1999-04-09 14:36 Chris Tessone
1999-04-09 15:04 ` Kai.Grossjohann
1999-04-09 15:07   ` Chris Tessone
1999-04-09 15:33     ` Kai.Grossjohann
1999-04-09 16:03       ` Colin Rafferty
1999-04-10  0:27       ` Stainless Steel Rat
1999-04-10 20:07         ` Christopher K Davis
1999-04-10 22:30         ` Kai.Grossjohann
1999-04-11  6:18           ` Stephen Zander
1999-04-11 13:49           ` Stainless Steel Rat
1999-04-11 14:48             ` Christopher K Davis
1999-04-11 18:16               ` Stainless Steel Rat
1999-04-11 19:21                 ` Christopher K Davis
1999-04-12  2:00                   ` Stainless Steel Rat
1999-04-12  2:35                     ` Christopher K Davis
1999-04-11 20:38                 ` Russ Allbery
1999-04-11 21:14                 ` Dan Christensen
1999-04-12  2:03                   ` Stainless Steel Rat
1999-04-11 16:20             ` Kai.Grossjohann
1999-04-11 18:24               ` Stainless Steel Rat
1999-04-11 19:15                 ` Kai.Grossjohann
1999-04-11 21:33                   ` Chris Tessone
1999-04-17  7:59                     ` Lars Magne Ingebrigtsen
1999-04-21  2:38                       ` Chris Tessone
1999-04-21 16:12                         ` Chris Tessone
1999-04-22 14:56                           ` Kai.Grossjohann
1999-04-22 20:59                             ` Chris Tessone
1999-04-21 21:40                         ` François Pinard
1999-04-11 19:18                 ` Kai.Grossjohann
1999-04-12  2:07                   ` Stainless Steel Rat
1999-04-12  2:36                     ` Christopher K Davis

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=vafpv5dlxyt.fsf@ramses.cs.uni-dortmund.de \
    --to=kai.grossjohann@cs.uni-dortmund.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).