From: Frank Schmitt <usereplyto@Frank-Schmitt.net>
Subject: Re: Limiting number of Incomingxxxx mails
Date: Fri, 14 Feb 2003 15:05:24 +0100 [thread overview]
Message-ID: <u7kc37yaj.fsf@hschmi22.userfqdn.rz-online.de> (raw)
In-Reply-To: <v91y2b0zkh.fsf@marauder.physik.uni-ulm.de>
Reiner Steib <4.uce.03.r.s@nurfuerspam.de> writes:
> On Fri, Feb 14 2003, Sriram Karra wrote:
>
> [ ~/Mail/Incomingxxx ]
>> What I am looking for is some way to tweak this feature such that it
>> will not take up too much disk space. (Recently I noticed that these
>> files accounted for ~65% of the size of ~/Mail/ :)
>>
>> What variables should I be looking at?
>
> I'm not aware of any predefined functionality in Gnus to do this.
WIBNIG had an option to automatically compress those files when storing
them on disk?
--
One Ring to rule them all, One Ring to find them,
One Ring to bring them all and in the darkness bind them
In the Land of Mordor where the Shadows lie.
next prev parent reply other threads:[~2003-02-14 14:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <xeq3r8abqkpm.fsf@desh.cisco.com>
2003-02-14 13:19 ` Reiner Steib
2003-02-14 14:05 ` Frank Schmitt [this message]
2003-02-17 4:56 ` Sriram Karra
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=u7kc37yaj.fsf@hschmi22.userfqdn.rz-online.de \
--to=usereplyto@frank-schmitt.net \
--cc=replies@Frank-Schmitt.net \
/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).