Gnus development mailing list
 help / color / mirror / Atom feed
From: "Paul D. Smith" <pausmith@nortelnetworks.com>
Subject: Incoming* turds?
Date: Tue, 12 Oct 1999 16:03:47 -0400 (EDT)	[thread overview]
Message-ID: <14339.37923.379781.86955@baynetworks.com> (raw)

Hope this hasn't been discussed to death; I just resubscribed after an
absence (due to email issues :-/).

My disk got full this morning and while cleaning up I discovered my
~/Mail directory had 2,300+ Incoming* files, dating from earlier this
summer when I first installed pgnus.

I've upgraded to pgnus 0.97 and I still get these, one for each nnfolder
archive I have that has mail whenever I do a "g".  They look like a
temporary file containing the contents of the spool file.

Emacs 20.4, pgnus 0.97, Solaris 2.5.1.
I use procmail to split my incoming mail into various spools, then
nnfolder to read them.

Thoughts on where to look?  Is some hook function returning improperly
such that the message retrieval isn't cleaning up?  Or is this a known
bug?

-- 
-------------------------------------------------------------------------------
 Paul D. Smith <psmith@baynetworks.com>         Network Management Development
 "Please remain calm...I may be mad, but I am a professional." --Mad Scientist
-------------------------------------------------------------------------------
   These are my opinions---Nortel Networks takes no responsibility for them.


             reply	other threads:[~1999-10-12 20:03 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-10-12 20:03 Paul D. Smith [this message]
1999-10-12 20:23 ` Paul Stevenson
1999-10-12 21:23   ` Paul D. Smith
1999-10-13  0:02     ` Stainless Steel Rat

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=14339.37923.379781.86955@baynetworks.com \
    --to=pausmith@nortelnetworks.com \
    /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).