From: Chris Shenton <cshenton@uucom.com>
Cc: ding@gnus.org
Subject: Re: Gnus-5.8.7 new groups status "*", can't enter; "Incoming*" files
Date: Mon, 31 Jul 2000 19:36:00 -0400 [thread overview]
Message-ID: <lflmyhx47z.fsf@Samizdat.uucom.com> (raw)
In-Reply-To: Cyrille Lefevre's message of "01 Aug 2000 01:17:53 +0200"
On 01 Aug 2000 01:17:53 +0200, Cyrille Lefevre <clefevre@citeweb.net> said:
Cyrille> try just g after you have created your new folder, or C-u
Cyrille> space or return, don't remember. I work this way, too, but w/
Cyrille> nnfolder :)
Bummer, no luck. I did "g" like I always to to injest mail, then tried
both C-u SPACE then C-u RETURN. No joy. From the *Messages* buffer:
Retrieving newsgroup: nnml:list.fw1-wizards@phoneboy.com...
Opening nnml server on +nnml:list.fw1-wizards@phoneboy.com...
Invalid group (no such directory)
Couldn't request group nnml:list.fw1-wizards@phoneboy.com: Invalid group (no such directory)
Retrieving newsgroup: nnml:list.fw1-wizards@phoneboy.com...
Invalid group (no such directory)
Couldn't request group nnml:list.fw1-wizards@phoneboy.com: Invalid group (no such directory)
But it lies:
/export/home/cshenton/Mail/list:
drwxr-sr-x 3 cshenton staff 512 Jul 24 09:30 fw1-wizards@phoneboy
>> 2. Leaves tmp files like ~/Mail/Incoming#####xyz
Cyrille> I have these, too.
Yikes, I have 6000 since the beginning of the July. (No wonder WAIS is
taking so long...)
next prev parent reply other threads:[~2000-07-31 23:36 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-07-31 13:19 Chris Shenton
2000-07-31 22:53 ` Kevin Falcone
2000-07-31 23:17 ` Cyrille Lefevre
2000-07-31 23:36 ` Chris Shenton [this message]
2000-08-01 2:06 ` Cyrille Lefevre
2000-08-01 2:52 ` Chris Shenton
2000-08-01 3:15 ` Cyrille Lefevre
2000-08-01 7:37 ` Kai Großjohann
2000-08-01 12:23 ` David S. Goldberg
2000-08-01 13:33 ` David S. Goldberg
2000-08-01 17:43 ` Chris Shenton
2000-08-02 8:31 ` Kai Großjohann
2000-08-02 14:49 ` Paul Jarc
2000-08-02 19:24 ` Kai Großjohann
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=lflmyhx47z.fsf@Samizdat.uucom.com \
--to=cshenton@uucom.com \
--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).