From: Daniel Pittman <daniel@rimspace.net>
To: ding@gnus.org
Subject: Re: gnus and imap
Date: Mon, 25 Aug 2008 10:00:50 +1000 [thread overview]
Message-ID: <8763pq6k0d.fsf@rimspace.net> (raw)
In-Reply-To: <878wumqo7z.fsf@randomsample.de>
David Engster <deng@randomsample.de> writes:
> Vitaly Mayatskikh <v.mayatskih@gmail.com> writes:
>>> Absolutely. The problem is that active information is used throughout
>>> Gnus, and the code is in parts already pretty convoluted, especially the
>>> ones dealing with updating groups and checking for unread messages. I
>>> guess that putting unread information in gnus-info would affect fewer
>>> parts of the code.
>>
>> Yes, but we still have to fix all this convoluted code (for
>> gnus-unread-info or whatever). Unread articles calculations (count of
>> articles, list of articles) are totally wrong for the case of IMAP.
>
> I wonder why it's that bad with the Zimbra imapd. Doesn't it produce
> contiguous UIDs?
No, it doesn't. They increment, I strongly suspect, on a partially time
based counter, or possibly an account-wide number of deliveries based
counter, since one email in a group overnight gets around the same total
UID increment as the Linux kernel list in the same period, with some
hundred.
I have not yet taken the time to see if they available source code
explains why this is, or if it can be fixed, but the UID space is
*definitely* non-contiguous in Zimbra.
(Which, yes, does rather suck.)
Regards,
Daniel
next prev parent reply other threads:[~2008-08-25 0:00 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-19 16:14 Vitaly Mayatskikh
2008-08-19 20:12 ` Frank Schmitt
2008-08-19 22:24 ` Vitaly Mayatskikh
2008-08-20 6:42 ` Vegard Vesterheim
2008-08-20 7:41 ` Vitaly Mayatskikh
2008-08-20 16:16 ` David Engster
2008-08-21 6:26 ` Vitaly Mayatskikh
2008-08-21 11:27 ` David Engster
2008-08-21 12:57 ` Tibor Simko
2008-08-22 8:44 ` Vitaly Mayatskikh
2008-08-22 8:54 ` David Engster
2008-08-22 15:35 ` Tibor Simko
2008-08-21 15:06 ` Vitaly Mayatskikh
2008-08-21 21:15 ` Frank Schmitt
2008-08-22 12:13 ` Reiner Steib
2008-08-22 12:30 ` Vitaly Mayatskikh
2008-08-22 15:50 ` Ted Zlatanov
2008-08-22 16:10 ` Vitaly Mayatskikh
2008-08-22 16:21 ` David Engster
2008-08-22 16:27 ` Vitaly Mayatskikh
2008-08-22 17:33 ` David Engster
2008-08-22 18:11 ` Vitaly Mayatskikh
2008-08-23 9:19 ` David Engster
2008-08-23 11:32 ` Vitaly Mayatskikh
2008-08-23 14:52 ` David Engster
2008-08-24 8:47 ` Vitaly Mayatskikh
2008-08-24 18:09 ` David Engster
2008-08-24 19:29 ` Reiner Steib
2008-08-24 23:39 ` David Engster
2008-08-25 19:22 ` James Cloos
2008-08-25 0:00 ` Daniel Pittman [this message]
2008-08-25 9:46 ` David Engster
2008-08-25 18:02 ` Ted Zlatanov
2008-08-25 19:50 ` David Engster
2008-08-25 8:05 ` Vitaly Mayatskikh
2008-08-25 12:25 ` David Engster
2008-08-25 13:17 ` Vitaly Mayatskikh
2008-08-25 17:53 ` Ted Zlatanov
2008-08-24 9:18 ` Vitaly Mayatskikh
2008-08-24 10:08 ` David Engster
2008-08-26 20:40 ` Vitaly Mayatskikh
2008-09-03 11:55 ` David Engster
2008-09-21 9:57 ` David Engster
2009-12-07 18:57 ` Dan Christensen
2009-12-10 20:08 ` Dan Christensen
2009-12-11 20:36 ` David Engster
-- strict thread matches above, loose matches on Subject: below --
2002-07-09 8:52 gnus and IMAP me
2002-07-09 9:29 ` Niklas Morberg
2002-07-09 10:17 ` me
2002-07-09 10:27 ` me
2002-07-09 10:52 ` me
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=8763pq6k0d.fsf@rimspace.net \
--to=daniel@rimspace.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).