From: Reiner Steib <4.uce.03.r.s@nurfuerspam.de>
Subject: Re: Deleted messages remain
Date: Fri, 28 Mar 2003 11:56:03 +0100 [thread overview]
Message-ID: <v9fzp7bvzw.fsf@marauder.physik.uni-ulm.de> (raw)
In-Reply-To: <84brzvesfi.fsf@lucy.is.informatik.uni-duisburg.de>
On Fri, Mar 28 2003, Kai Großjohann wrote:
> Peter Wu <peterwu@hotmail.com> writes:
>
>> Incoming142JtR Incoming187-C5 Incoming256GH5 drafts/
>> Incoming175UQS Incoming232ckH active mail/
>
> The Incoming files are a safety net. You're running an alpha version
> of Gnus which might eat your mail for breakfast. When that happens,
> you have a copy right there.
Peter, if your Oort is newer than 2003-03-03, you may want to set
`mail-source-delete-incoming' to a number, see the manual:
,----[ (Info-goto-node "(gnus)Mail Source Customization") ]
| `mail-source-delete-incoming'
| If non-`nil', delete incoming files after handling them. If `t',
| delete the files immediately, if `nil', never delete any files.
| If a positive number, delete files older than number of days (This
| will only happen, when reveiving new mail). You may also set
| `mail-source-delete-incoming' to `nil' and call
| `mail-source-delete-old-incoming' from a hook or interactively.
|
| `mail-source-delete-old-incoming-confirm'
| If `non-nil', ask for for confirmation before deleting old incoming
| files. This variable only applies when
| `mail-source-delete-incoming' is a positive number.
`----
Bye, Reiner.
--
,,,
(o o)
---ooO-(_)-Ooo--- PGP key available via WWW http://rsteib.home.pages.de/
prev parent reply other threads:[~2003-03-28 10:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <86y936lquu.fsf@vanilla.zzz>
2003-03-22 14:21 ` Jacob Bunk Nielsen
[not found] ` <84brzvesfi.fsf@lucy.is.informatik.uni-duisburg.de>
2003-03-28 10:56 ` Reiner Steib [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=v9fzp7bvzw.fsf@marauder.physik.uni-ulm.de \
--to=4.uce.03.r.s@nurfuerspam.de \
--cc=reiner.steib@gmx.de \
/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).