Cyrus is an excellent server, and I have no difficulty in recommending
Cyrus for a site that seems to be a good match for it.
There is very little overlap between the user communities of Cyrus and UW
imapd. Cyrus is best for those sites which want a more black-box
environment with Cyrus based administrative controls (and not be affected
or limited by UNIX administration). UW is best for sites which want IMAP
service in conjunction with other services and want IMAP to obey their
UNIX administration decisions.
Some sites run both, depending upon their environment. I don't currently
run a Cyrus server, but I can envision myself doing so in certain
situations. I imagine that the Cyrus folks would say the same things
about UW.
One plus in UW imapd's column is that its driver architecture makes it
possible for you (or anyone else) to create your own mailbox format and
have UW imapd support it. With Cyrus, you are committed to Cyrus format.
In theory, UW could support Cyrus format. However, the exercise would be
pointless. UW wouldn't have Cyrus' admin tools, and you'd have to make
the files use the UNIX ownership model rather than Cyrus' ownership model.
Nor would it gain anything; Cyrus specializes in being Cyrus, while UW is
a generalist. Thus, Cyrus (by definition!) is a better Cyrus. ;-)
Since mix should resolve your performance requirements, I think that your
decision about Cyrus vs. UW should be based upon your feature set
requirements. It seems to me that Cyrus' feature set isn't in your
current requirements list.
It's like asking, which is better, an SUV or a sports car? It all
depends, doesn't it!
-- 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
