From: Lars Magne Ingebrigtsen <larsi@gnus.org>
Subject: Re: [lconrad@world.std.com] Re: lots of Incoming* files in Mail directory
Date: 12 Jun 1999 04:13:27 +0200 [thread overview]
Message-ID: <m3emji9neg.fsf@quimbies.gnus.org> (raw)
In-Reply-To: lconrad@world.std.com's message of "19 Apr 1999 23:08:56 -0400"
lconrad@world.std.com writes:
> Better (or at least more) information. The one that just happened was
> a case where fetchmail had fetched 3 messages; gnus did sort them into
> the right newsgroups, and I did read them there, but for some reason
> it also left an Incoming file in the Mail directory.
Yes, alpha versions of Gnus are supposed to save all incoming mail in
the Incoming* files. For safekeeping, in case something went wrong.
Just delete them as your disks run full.
--
(domestic pets only, the antidote for overdose, milk.)
larsi@gnus.org * Lars Magne Ingebrigtsen
next parent reply other threads:[~1999-06-12 2:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <m31zhgrnsn.fsf@serpent.laymusic.>
1999-06-12 2:13 ` Lars Magne Ingebrigtsen [this message]
1999-04-20 3:08 lconrad
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=m3emji9neg.fsf@quimbies.gnus.org \
--to=larsi@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).