nnimap: incorrect number of unread articles

nnimap: incorrect number of unread articles

[Vladimir Volovich]

Hi,

when i receive some articles into an IMAP folder, i see some counter
in the groups buffer for that group. Let's assume it's value is 100.

Then i remove some most recent mesages (say, 5), and return to the
Groups buffer.

The number shown is: 95, which os correct.

Then i receive a new message in that mail folder (g).

The number shown is not 96, but 101!

Such behavior is very consistent and reproduceable.

Best,
v.

Re: nnimap: incorrect number of unread articles

[Simon Josefsson]

Vladimir Volovich <vvv@vsu.ru> writes:

> The number shown is not 96, but 101!

Please see the `Group Line Specification' node in the documentation:

...

`t'
     Estimated total number of articles.  (This is really MAX-NUMBER
     minus MIN-NUMBER plus 1.)

     Gnus uses this estimation because the NNTP protocol provides
     efficient access to MAX-NUMBER and MIN-NUMBER but getting the true
     unread message count is not possible efficiently.  For hysterical
     raisins, even the mail backends, where the true number of unread
     messages might be available efficiently, use the same limited
     interface.  To remove this restriction from Gnus means that the
     backend interface has to be changed, which is not an easy job.  If
     you want to work on this, please contact the Gnus mailing list.

Re: nnimap: incorrect number of unread articles

[Kai Großjohann]

Well, Gnus uses lowest and highest article number to estimate the
unread article count.  This estimate is used in the *Group* buffer.
Gnus uses an estimate for hysterical raisins having to do with
efficiency: it is possible to quickly get the lowest and highest
article number for a group via NNTP, but to get the actual article
count you have to actually enter the group which is much slower.

kai
-- 
~/.signature: No such file or directory