From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.general/36202 Path: main.gmane.org!not-for-mail From: Simon Josefsson Newsgroups: gmane.emacs.gnus.general Subject: Re: IMAP trouble - and my memory's gone, too... Date: 12 May 2001 10:56:48 +0200 Message-ID: References: NNTP-Posting-Host: coloc-standby.netfonds.no Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: main.gmane.org 1035171828 7300 80.91.224.250 (21 Oct 2002 03:43:48 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Mon, 21 Oct 2002 03:43:48 +0000 (UTC) Cc: The Gnus Mailing List Return-Path: Original-Received: (qmail 15721 invoked by alias); 12 May 2001 08:56:51 -0000 Original-Received: (qmail 15710 invoked from network); 12 May 2001 08:56:50 -0000 Original-Received: from dolk.extundo.com (195.42.214.242) by gnus.org with SMTP; 12 May 2001 08:56:50 -0000 Original-Received: from barbar.josefsson.org (slipsten.extundo.com [195.42.214.241]) (authenticated) by dolk.extundo.com (8.11.3/8.11.3) with ESMTP id f4C8upq02476; Sat, 12 May 2001 10:56:51 +0200 Original-To: "Robin S. Socha" In-Reply-To: ("Robin S. Socha"'s message of "12 May 2001 03:47:42 +0200") Mail-Copies-To: nobody User-Agent: Gnus/5.090004 (Oort Gnus v0.04) Emacs/21.0.103 Original-Lines: 24 Xref: main.gmane.org gmane.emacs.gnus.general:36202 X-Report-Spam: http://spam.gmane.org/gmane.emacs.gnus.general:36202 "Robin S. Socha" writes: > | nnimap: Group INBOX is not uidvalid. Continue? (y or n) Answer yes. I think then it will replace the uidvalidity value on the group and then proceed. Possibly some things are now corrupt (like the NOV cache in ~/News/overview/nnimap.), but probably not. The proper solution is to make Gnus wipe out everything (flags, cache, agent etc) it knows about the group and sync it from the server again, but a backend can't tell Gnus to do that today. So instead nnimap asks the user a cryptic question, and whatever the user answers he will suspect that he created the problem and not nnimap. :) Not good, I know. > | (2) (memory/critical) Warning: past 85% of memory limit > | Killing some buffers may delay running out of memory. > | However, certainly by the time you receive the 95% warning, > | you should clean up, kill this Emacs, and start a new one. Well, how large is your emacsen? Perhaps the gnus-range functions take a lot of memory if it has to operate on a huge range, like expanding the range (1 . 10000000). Also, imap.el caches some stuff from the server.