From: Jacob Bunk Nielsen <spam@bunk.cc>
Subject: Re: Deleted messages remain
Date: Sat, 22 Mar 2003 15:21:21 +0100 [thread overview]
Message-ID: <spamdrop+m3isubcwim.fsf@paven.bunk.cc> (raw)
In-Reply-To: <86y936lquu.fsf@vanilla.zzz>
Peter Wu <peterwu@hotmail.com> writes:
> However, after deleting some junk mails by hitting B-Del, the
> messages remain on the hard disk.
>
>> ls ~/Mail/
> Incoming142JtR Incoming187-C5 Incoming256GH5 drafts/
> Incoming175UQS Incoming232ckH active mail/
>
> Is this behavior expected? Thanks.
This is because you use Oort Gnus. It is default behavior for Oort
Gnus (which is under heavy development) to have
mail-source-delete-incoming set to nil. You can either set it to some
number (number of days before incoming mails are deleted) or to t (as
is default in officially released Gnusae), which will delete all
incoming mails.
--
Jacob - www.bunk.cc
You can always tell luck from ability by its duration.
next parent reply other threads:[~2003-03-22 14:21 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 [this message]
[not found] ` <84brzvesfi.fsf@lucy.is.informatik.uni-duisburg.de>
2003-03-28 10:56 ` Reiner Steib
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=spamdrop+m3isubcwim.fsf@paven.bunk.cc \
--to=spam@bunk.cc \
/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).