From: Phillip Lord <phillip.lord@newcastle.ac.uk>
Subject: Re: Buffer exceeds maximum size
Date: Thu, 30 Mar 2006 19:43:11 +0100 [thread overview]
Message-ID: <u64lvepts.fsf@newcastle.ac.uk> (raw)
In-Reply-To: <yxdacb7g5g1.fsf@cs1.gmu.edu>
>>>>> "MA" == Myriam Abramson <mabramso@cs1.gmu.edu> writes:
MA> Just to answer my own question, I found out that I split my mail
MA> with nnmail into separate folders and those folders just got too
MA> big. Deleting the folder (that is the file corresponding to the
MA> folder) solved the problem. Maybe that could be handled better,
MA> so that only the last n messages are loaded. Anyway, I am glad I
MA> solved my problem so that I can continue using gnus for email
Have you though about setting up auto-expiry; if you archive your
messages after a year or so, to a year archive group you should be
alright?
Or you could try moving to a 1 file per message backend; although this
is likely to create a lot of files, unless you get few mails with huge
attachments.
Cheers
Phil
prev parent reply other threads:[~2006-03-30 18:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <yxdwtecdkdr.fsf@cs1.gmu.edu>
2006-03-30 16:51 ` Karl Kleinpaste
[not found] ` <yxdacb7g5g1.fsf@cs1.gmu.edu>
2006-03-30 18:43 ` Phillip Lord [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=u64lvepts.fsf@newcastle.ac.uk \
--to=phillip.lord@newcastle.ac.uk \
/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).