From: Julien Danjou <julien@danjou.info>
To: Dan Christensen <jdc@uwo.ca>
Cc: ding@gnus.org
Subject: Re: Returning to ticks on read-only imap servers
Date: Sat, 09 Oct 2010 08:57:23 +0200 [thread overview]
Message-ID: <87aamnq2ek.fsf@keller.adm.naquadah.org> (raw)
In-Reply-To: <87r5g0mkuk.fsf@uwo.ca> (Dan Christensen's message of "Fri, 08 Oct 2010 17:32:35 -0400")
[-- Attachment #1: Type: text/plain, Size: 606 bytes --]
On Fri, Oct 08 2010, Dan Christensen wrote:
> I'm no expert, but my understanding is that in normal operation,
> UIDVALIDITY never changes, even when messages arrive, are deleted, or
> flags change. So it can't help solve the problem at hand.
That's totally the opposite. A UIDVALIDITY number design a mailbox in a
state. If any change occurs, the UIDVALIDITY number changes. That's how
you know you need to do a FETCH 1:* to resynchronize your (cached)
version of the mailbox.
Read section 2.3.1.1 of RFC3501.
--
Julien Danjou
// ᐰ <julien@danjou.info> http://julien.danjou.info
[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2010-10-09 6:57 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-05 19:16 Michael Welsh Duggan
2010-10-05 20:25 ` Steinar Bang
2010-10-05 21:01 ` Michael Welsh Duggan
2010-10-07 18:59 ` Lars Magne Ingebrigtsen
2010-10-07 21:37 ` Michael Welsh Duggan
2010-10-07 22:40 ` Lars Magne Ingebrigtsen
2010-10-08 15:07 ` James Cloos
2010-10-08 17:00 ` Lars Magne Ingebrigtsen
2010-10-08 18:22 ` Julien Danjou
2010-10-08 18:26 ` Lars Magne Ingebrigtsen
2010-10-08 18:28 ` Julien Danjou
2010-10-08 18:49 ` Lars Magne Ingebrigtsen
2010-10-08 19:34 ` Julien Danjou
2010-10-08 21:32 ` Dan Christensen
2010-10-09 6:57 ` Julien Danjou [this message]
2010-10-09 8:10 ` Michael Welsh Duggan
2010-10-09 8:26 ` Julien Danjou
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=87aamnq2ek.fsf@keller.adm.naquadah.org \
--to=julien@danjou.info \
--cc=ding@gnus.org \
--cc=jdc@uwo.ca \
/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).