Unfortunately, the design of UIDPLUS support precludes partial
implementation. Even worse, UIDPLUS is mandatory if the server advertises
it; so a client which does not use UIDPLUS must still pay the cost.
I complained about these characteristics bitterly, as I knew that it would
be a problem for traditional UNIX format. My argument did not sway the
day. I did not write the UIDPLUS specification either, although I did
update it to ameliorate its worst aspects.
This is why I did not implement UIDPLUS for quite some time. Sadly, the
advent of clients which do not work without UIDPLUS (e.g., Eudora) and
other factors made this no longer viable.
Fortunately, the primary cost is one-time per mailbox, as long as
subsequent access is through the new code. If the mailbox is subsequently
accessed via old code you may experience the large hit again. As this is
an issue for you, I strongly recommend that you try the latest imap-2006d
development snapshot, as there are performance improvements for
traditional UNIX format with UIDPLUS in that version.
Similarly, yes, I recommend that you rebuild Pine 4.64 to use the
imap-2006d version of c-client and/or try Alpine (which contains the
imap-2006d c-client).
There is a smaller hit with traditional UNIX format that is unavoidable.
It should be much less costly than the big hit; however, if you really
have 940MB traditional UNIX mailbox format mailboxes you should seriously
consider using another format for other reasons.
You should also see if your clients implement aggregate COPY and
MULTIAPPEND (Pine does) since the cost is per-copy operation and not per
message unless you do a single-message copy.
I'm very sorry that you have to go through all this.
-- Mark --
http://staff.washington.edu/mrc
Science does not emerge from voting, party politics, or public debate.
Si vis pacem, para bellum.
_______________________________________________
Imap-uw mailing list
[email protected]
https://mailman1.u.washington.edu/mailman/listinfo/imap-uw
