From: Michael Widerkrantz <mc@hack.org>
To: info-gnus-english@gnu.org
Subject: Re: An Idea for Gnus
Date: Sat, 10 Nov 2007 14:17:13 +0100 [thread overview]
Message-ID: <86ode2p7dy.fsf@brain.hack.org> (raw)
In-Reply-To: <m3wsss7oxj.fsf@ieee.org>
Randy Yates <yates@ieee.org> writes:
> Due to the way gnus stores sent mail in one long file, that
> file has grown to be quite large, and now every time I send a mail
> it takes some number of seconds for gnus just to append the sent
> mail to the end of that file.
Do you use a single nnfolder for archiving all your outgoing messages?
You can fix this in a number of ways. One way is to automatically
create a new nnfolder every month, like this:
;;; Archive my outgoing messages, both mail and news in a group called
;;; out.year-month. Use the nnfolder backend for the archives.
(setq gnus-message-archive-group
'((concat "out." (format-time-string
"%Y-%m" (current-time)))))
I keep them in a Topic called "Outgoing archive" and get a list like
this on the top level:
Outgoing archive: 12190
out.1999-05: 15 (77)
out.1999-06: 110 (118)
out.1999-07: 69 (88)
out.1999-08: 196 (197)
out.1999-09: 280 (350)
...
out.2007-11: 118 (127)
The number in parentheses are the total number of messages in that
folder. Taken together they all currently take up 65 MB worth of sent
messages since May 1999 when I had this configuration set up. I send
very little attachments, so this is mostly text written by me. Wow.
--
MC, http://hack.org/mc/
prev parent reply other threads:[~2007-11-10 13:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-07 22:38 Randy Yates
2007-11-08 10:00 ` Michael Widerkrantz
[not found] ` <mailman.3123.1194516062.18990.info-gnus-english@gnu.org>
2007-11-08 15:11 ` Randy Yates
2007-11-08 16:00 ` It's me FKtPp ;)
2007-11-08 17:11 ` Scott Gifford
2007-11-10 13:17 ` Michael Widerkrantz [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=86ode2p7dy.fsf@brain.hack.org \
--to=mc@hack.org \
--cc=info-gnus-english@gnu.org \
/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).