On Mon, Jan 12, 2015 at 10:13 AM, René J.V. <[email protected]> wrote:
> > I stopped running uw-imap that a long time ago because of similar issues > (data corruption especially under high load) and also because of a series > of security issues that happened one after another (that I got sick of > dealing with/patching). IIRC uw-imapd went from keeping the mailbox locked (low/no corruption, but clients error out a lot because they reasonably expect concurrent access) to locking only when "necessary" (gets it wrong a lot, partly due to concurrent delivery by MTAs, high corruption), as email volume increased from the fairly low levels when it was first written. In either mode it's a pretty lousy server even for single user use. BITD it was acceptable, but email is much higher volume these days and there are much more appropriate IMAP servers. Yes, you can get lucky for a while. No, past performance is no guarantee whatsoever of future results. -- brandon s allbery kf8nh sine nomine associates [email protected] [email protected] unix, openafs, kerberos, infrastructure, xmonad http://sinenomine.net
_______________________________________________ macports-users mailing list [email protected] https://lists.macosforge.org/mailman/listinfo/macports-users
