On Mon, 27 Jan 2003, Cyrus Daboo wrote:
> The only caveat is for servers that do not use timestamps for UIDVALIDITY.
> In that case those servers would have to ensure that the new UIDVALIDITY is
> greater than any UIDVALIDITY for mailboxes that may have previously existed
> with any of the new names.
What happens if the UIDVALIDITY of an inferior name can't be changed, such
as when ACLs prohibit it or if there's a loop in the hierarchy tree?
Consider the case of:
% mkdir foo
% mailutil create foo/bar
% ln -s foo/zap /
Now in IMAP, we do
a001 RENAME foo garp
We now have garp/bar and garp/zap. How is the UIDVALIDITY to be fixed
with all the names in garp/zap/*? Note that this has to be done without
altering the UIDVALIDTY in /*.
I repeat my assertation: RENAME is fundamentally broken and should be
removed from IMAP.
-- Mark --
http://staff.washington.edu/mrc
Science does not emerge from voting, party politics, or public debate.
