Gnus development mailing list
 help / color / mirror / Atom feed
From: Wes Hardaker <wjhardaker@ucdavis.edu>
Subject: Re: mail archival idea/feature request
Date: 01 Sep 1999 09:53:43 -0700	[thread overview]
Message-ID: <x7906qr2so.fsf@homestyle.dcn.davis.ca.us> (raw)
In-Reply-To: Lars Magne Ingebrigtsen's message of "27 Aug 1999 19:39:46 +0200"

>>>>> On 27 Aug 1999 19:39:46 +0200, Lars Magne Ingebrigtsen <larsi@gnus.org> said:

Lars> Or -- the old, expirable articles are deleted, and the old,
Lars> non-expirable articles are moved to the archive group.  Hee hee.

That'd work too (though in some cases I want to pick when things move
to the archive group (and I want to archive everything) and when they
stick around as old (hence, E).

It comes from disk space being so cheap and most mail messages being
so small...  Why not just archive my entire life.

Quick calculations;
  Random sample of my old nnml inbox (now using nnimap):

  % ls -l | wc -l
      325
  % ls -l | awk '{total = total + $5} END { print (total/325); }'
  17278

Ok, so each message is on average 17k.  (most are much much smaller,
and a threshold on the max size archived would be even better).

I get about 300 messages a day at last count.  Ok, lets count
yesterday just to be sure:

% grep "Aug 30" MAIL_LOG | grep '^From' | wc -l
    287

Yep, still roughly accurate.

So, how much space for a years worth of messages?

  (* 17 300 365) = 1.8gig.

So, I'd gladly waste a 1.8 gig disk to archive my entire years worth
of mail providing I didn't have to store it in the current folder
where it would eat away my summary buffer creation speed.

However, I would not of course archive my entire set of mail lists.
Mostly important groups like inbox, work, etc, which would reduce the
size of the above as well.

So, uh, got it written yet?

-- 
"Ninjas aren't dangerous.  They're more afraid of you than you are of them."


  reply	other threads:[~1999-09-01 16:53 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-07-09 18:27 Andrew Hobson
1999-07-09 21:04 ` Lars Magne Ingebrigtsen
1999-07-09 21:39   ` Andrew Hobson
1999-07-11  8:58     ` Lars Magne Ingebrigtsen
1999-07-09 22:49 ` Kai.Grossjohann
1999-07-10 13:53   ` Andrew Hobson
1999-07-10 21:23     ` Kai.Grossjohann
1999-07-12 14:50       ` Andrew Hobson
1999-07-12 15:24       ` Karl Kleinpaste
1999-07-12 15:52   ` Wes Hardaker
1999-07-12 16:13     ` Kai Großjohann
1999-07-12 15:55 ` Wes Hardaker
1999-08-27 17:39   ` Lars Magne Ingebrigtsen
1999-09-01 16:53     ` Wes Hardaker [this message]
1999-09-01 19:06       ` Andrew Hobson
1999-09-03 21:32         ` Wes Hardaker
1999-09-03 22:11           ` Andrew Hobson
1999-09-07 17:33             ` Wes Hardaker
1999-09-25  7:51         ` Lars Magne Ingebrigtsen

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=x7906qr2so.fsf@homestyle.dcn.davis.ca.us \
    --to=wjhardaker@ucdavis.edu \
    /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).