From: "Paul D. Smith" <pausmith@nortelnetworks.com>
Cc: Ding Mailing List <ding@gnus.org>
Subject: Re: Incoming* turds?
Date: Tue, 12 Oct 1999 17:23:25 -0400 (EDT) [thread overview]
Message-ID: <14339.42701.492648.292580@baynetworks.com> (raw)
In-Reply-To: <m2r9j0pbue.rhythmically@bethe.phy.ornl.gov>
%% Paul Stevenson <spaul@mail.phy.ornl.gov> writes:
ps> "Paul D. Smith" <pausmith@nortelnetworks.com> writes:
>> 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.
ps> That's because pgnus is alpha software and hence could potentially do
ps> nasty things to your mail. This saving raw copies of your mail is a
ps> safeguard against bad things happening.
OK... I don't have any good ideas about how, but it would have been nice
to know it was going to do that so I could have deleted them sooner.
I only use Gnus to read mailing lists and, well, if I miss a mail here
and there on those it's no big deal :).
>> Thoughts on where to look?
ps> I tried M-x apropos RET incoming RET
ps> It gave, as its first entry the promising-sounding
ps> `mail-source-delete-incoming'
I saw that, but the help isn't very descriptive. I thought it
controlled whether or not the mail was left in the spool file after
copying or not.
Anyway, thanks!
--
-------------------------------------------------------------------------------
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.
next prev parent reply other threads:[~1999-10-12 21:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-10-12 20:03 Paul D. Smith
1999-10-12 20:23 ` Paul Stevenson
1999-10-12 21:23 ` Paul D. Smith [this message]
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.42701.492648.292580@baynetworks.com \
--to=pausmith@nortelnetworks.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).