Hi,
On 28 Jan 2003 19:35:16 +0200, Timo Sirainen <[EMAIL PROTECTED]> wrote...
> On Tue, 2003-01-28 at 09:52, Mark Keasling wrote:
> > This is not true. The UIDVALIDITY must be only be different.
> > Only servers that can not preserve UID values between sessions are required to
> > use ascending uidvality values.
>
> No, read more carefully:
>
> > If unique identifiers from an earlier session fail to persist to this
> > session, the unique identifier validity value MUST be greater than
> > the one used in the earlier session.
>
> "If UIDs aren't the same as last time, UIDVALIDITY must be grown."
Okay you are right. I was remembering an ancient situation were the
server couldn't maintain uids in its mailstore and blah blah blah which
no longer applies. That and the usage of different and greater than
to mean the same thing got me confused.
Excerpting the RFC...
A)
If unique identifiers from an
earlier session fail to persist to this session, the unique
identifier validity value MUST be greater than the one used in the
earlier session.
B)
However, if it is
not possible to preserve the unique identifier of a message in a
subsequent session, each subsequent session MUST have a new unique
identifier validity value that is larger than any that was used
previously.
C)
Another cause of non-persistance is if the mailbox is deleted and
a new mailbox with the same name is created at a later date, Since
the name is the same, a client may not know that this is a new
mailbox unless the unique identifier validity is different.
D)
If a new mailbox is created with the same name as a mailbox which
was deleted, its unique identifiers MUST be greater than any
unique identifiers used in the previous incarnation of the mailbox
UNLESS the new incarnation has a different unique identifier
validity value.
E)
The value of the highest-used unique identifier of the deleted
mailbox MUST be preserved so that a new mailbox created with the
same name will not reuse the identifiers of the former
incarnation, UNLESS the new incarnation has a different unique
identifier validity value.
F)
The value of the highest-used unique identifier of the old mailbox
name MUST be preserved so that a new mailbox created with the same
name will not reuse the identifiers of the former incarnation,
UNLESS the new incarnation has a different unique identifier
validity value.
CDEF conflicts with AB. A client has no way of knowing whether or
not the mailbox was deleted and created again since the last time it
was accessed. In the CDEF cases, the requirement is the uids are greater
than the previous mailbox with the same name or the validity value must
be different. Even in this case, the uid validity should be greater than
before not merely different since the server was not able to preserve
the uids between sessions.
Regards,
Mark Keasling <[EMAIL PROTECTED]>
