Gnus development mailing list
 help / color / mirror / Atom feed
From: Frank Schmitt <ich@frank-schmitt.net>
To: ding@gnus.org
Subject: Re: Bug in nnimap?
Date: Wed, 01 Sep 2010 20:24:26 +0200	[thread overview]
Message-ID: <871v9diap1.fsf@mid.gehheimdienst.de> (raw)
In-Reply-To: <87occh2whw.fsf@gmx.ch>

"Sven Bretfeld" <sven.bretfeld@gmx.ch> writes:

> Hi to all
>
> I'm using Gnus as an imap client since two years now. What annoys me
> ever since, is that Gnus keeps record of old mail headers of long
> deleted emails (not expired, deleted!).
>
> When entering a Group with C-u, Gnus asks if I want to see the several
> thousands of messages in that group. In reality there are only about one
> or two hundred mails within that imap folder. But Gnus actually displays the
> headers of every email that had ever lived in that group -- no matter if
> it's long deleted or shifted to another imap-folder. The Summary buffer
> displays the headers with the "O" mark, turning to "G" when one selects
> the message.
>
> This is annoying, especially if you have to worry about space
> limitations on the server. Gnus is not capable to tell how many mails
> actually exist in the respective folder.
>
> Is that a bug in nnimap? Is it a feature? Can somebody tell me how to
> prevent Gnus from keeping track of old headers or how to refresh its
> memory? 
>
> Can anybody even reproduce that behavior?

I regularly watch #gnus on freenode and this comes up very
frequently. The solution is to turn off Gnus agent.

-- 
Have you ever considered how much text can fit in eighty columns?  Given that a
signature typically contains up to four lines of text, this space allows you to
attach a tremendous amount of valuable information to your messages.  Seize the
opportunity and don't waste your signature on bullshit that nobody cares about.




  reply	other threads:[~2010-09-01 18:24 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-01 17:40 Sven Bretfeld
2010-09-01 18:24 ` Frank Schmitt [this message]
2010-09-03 14:33   ` Sven Bretfeld
2010-09-03 15:54   ` Tibor Simko
2010-09-03 17:33     ` Frank Schmitt
2010-09-03 17:37       ` Lars Magne Ingebrigtsen
2010-09-03 20:20         ` Steinar Bang
2010-09-03 20:22           ` Lars Magne Ingebrigtsen
2010-09-05  3:13           ` Tibor Simko
2010-09-03 19:38     ` Sven Bretfeld
2010-09-03 20:28       ` Steinar Bang
2010-09-03 20:22     ` Steinar Bang
2010-09-03 20:41       ` Frank Schmitt
2010-09-03 21:08         ` Steinar Bang
2010-09-05  2:47       ` Tibor Simko
2010-09-05  7:20         ` Steinar Bang
2010-09-03 20:25   ` Steinar Bang
2010-09-03 20:49     ` Lars Magne Ingebrigtsen
2010-09-03 21:08       ` Steinar Bang
2010-09-02  9:32 ` Gijs Hillenius
2010-09-03 14:35   ` Sven Bretfeld

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=871v9diap1.fsf@mid.gehheimdienst.de \
    --to=ich@frank-schmitt.net \
    --cc=ding@gnus.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).