Gnus development mailing list
 help / color / mirror / Atom feed
From: Karl Kleinpaste <karl@charcoal.com>
Subject: Re: IncomingXXXX files are not deleted.
Date: Tue, 04 Sep 2001 06:43:38 -0400	[thread overview]
Message-ID: <vxkae0bme1x.fsf@cinnamon.vanillaknot.com> (raw)
In-Reply-To: <m3lmjvwn3o.fsf@ournature.org> (Jinhyok Heo's message of "Tue, 04 Sep 2001 14:18:03 +0900")

Jinhyok Heo <novembreN0$PAM@ournature.org> writes:
> Why are they not deleted?

Because you're using an alpha version of Gnus.

In released versions, after being moved to a 5.x numbering scheme
without a name (currently "Oort"), mail-source-delete-incoming is set
to t, so that these temporary files are deleted.  But as long as a
development tree is in progress and not considered "released," it is
set to nil.  This is to forestall disaster during development in case
something to do with mail backend development gets seriously bugged,
so you don't actually lose mail.  This was actually very important
during the Pterodactyl Gnus series around the p0.40 time frame --
Lars' complete rework of backends caused some problems for POP users
and recovering from Gnus-induced disasters was really needed for a
little while then.  (Pterodactyl Gnus is what became 5.8, as released.)

If you are sufficiently confident of Gnus' mail source handling, set
the variable to t yourself in .gnus.  If not, you need to make sure
now and then that you delete these files manually, or perhaps instead
do so occasionally via cron, using find(1) with, say, "-mtime +5".


      reply	other threads:[~2001-09-04 10:43 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-04  5:18 Jinhyok Heo
2001-09-04 10:43 ` Karl Kleinpaste [this message]

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=vxkae0bme1x.fsf@cinnamon.vanillaknot.com \
    --to=karl@charcoal.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).