Fwd: [Imap-uw] inbox corruption by iphone
Based on the below I would like to suggest that imap-uw, which hasnt been updated since the author's death, be replaced with panda-imap, which solved at least my problem. Brian -- Forwarded message -- From: David B FunkDate: Sat, Aug 1, 2015 at 7:59 AM Subject: Re: [Imap-uw] inbox corruption by iphone To: brian Cc: UW imap list Have you tried the "Panda IMAP" distro? https://github.com/jonabbey/panda-imap The mailbox locking problem can be avoided by using an alternate form of mailbox (such as MIX) instead of the traditional mbox. Of course this won't work in an environment that requires local direct access to the mailbox by non-C-client aware mail clients. If you can switch to MIX format there are many advantages (performance, scale-ability, backup facilitation, etc). However if you do switch to MIX be -sure- to run the Panda distro, there were some unfixed bugs in the UW-imap distro that can bite you. After Mark left UW he started his own company with a fork of the UW-imap which he called "Panda" and then started developing a commercial product from there. He kept Panda alive and semi-open sourced, making bug-fixes and adding some small improvements (I know from conversations I had with him in '09 about a UW-imap bug I found/fixed ). He made it available to people who explicitly asked him for it. After his death people took the last known version of Panda and turned it into a github project and made additional improvements to it (I contributed one of them ;). On Sat, 1 Aug 2015, brian wrote: as expected, thanx for confirming. > > Brian > > On 8/1/2015 1:25 AM, Chris Bunch wrote: > >> I have been running a UW_IMAP server on Mac OS X mainly for family >> accounts for around 12 years. We are all Mac/iOS users: we noted early on >> that UW_IMAP doesn't cope well with more than one client logged into an >> account at the same time. When the most any of us had was two machines >> (home/office or home/laptop) that was relatively easy to manage but when >> iOS came along(iPhones, iPads) came along things began to unravel and the >> situation became unworkable. iPhones never stayed in sync with the server, >> though I have not seen the specific corruption you mention. >> >> I am now in the process of transferring family accounts to Fastmail and >> am setting up Dovecot on Linode/Ubuntu for a few other accounts I manage. >> Sadly, UW_IPAD’s future died with Mark Crispin. >> >> C >> >> >> >> On 22 Jul 2015, at 08:57, brian wrote: >>> >>> One of the users on my freebsd server that runs uw imap has an >>> intermittent problem with inbox corruption. Is a fix planned? I see others >>> have had this issue already. I am essentially seeing this >>> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=557103 though on >>> Freebsd. >>> >>> >>> Brian >>> >> -- Dave Funk University of Iowa College of Engineering 319/335-5751 FAX: 319/384-0549 1256 Seamans Center Sys_admin/Postmaster/cell_adminIowa City, IA 52242-1527 #include Better is not better, 'standard' is better. B{ ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Fwd: [Imap-uw] inbox corruption by iphone
Based on the below it seems the imap-uw port ought to go to an unsupported state or be otherwise modified? Brian -- Forwarded message -- From: David B Funk Date: Sat, Aug 1, 2015 at 7:59 AM Subject: Re: [Imap-uw] inbox corruption by iphone To: brian Cc: UW imap list imap...@u.washington.edu Have you tried the Panda IMAP distro? https://github.com/jonabbey/panda-imap The mailbox locking problem can be avoided by using an alternate form of mailbox (such as MIX) instead of the traditional mbox. Of course this won't work in an environment that requires local direct access to the mailbox by non-C-client aware mail clients. If you can switch to MIX format there are many advantages (performance, scale-ability, backup facilitation, etc). However if you do switch to MIX be -sure- to run the Panda distro, there were some unfixed bugs in the UW-imap distro that can bite you. After Mark left UW he started his own company with a fork of the UW-imap which he called Panda and then started developing a commercial product from there. He kept Panda alive and semi-open sourced, making bug-fixes and adding some small improvements (I know from conversations I had with him in '09 about a UW-imap bug I found/fixed ). He made it available to people who explicitly asked him for it. After his death people took the last known version of Panda and turned it into a github project and made additional improvements to it (I contributed one of them ;). On Sat, 1 Aug 2015, brian wrote: as expected, thanx for confirming. Brian On 8/1/2015 1:25 AM, Chris Bunch wrote: I have been running a UW_IMAP server on Mac OS X mainly for family accounts for around 12 years. We are all Mac/iOS users: we noted early on that UW_IMAP doesn't cope well with more than one client logged into an account at the same time. When the most any of us had was two machines (home/office or home/laptop) that was relatively easy to manage but when iOS came along(iPhones, iPads) came along things began to unravel and the situation became unworkable. iPhones never stayed in sync with the server, though I have not seen the specific corruption you mention. I am now in the process of transferring family accounts to Fastmail and am setting up Dovecot on Linode/Ubuntu for a few other accounts I manage. Sadly, UW_IPAD’s future died with Mark Crispin. C On 22 Jul 2015, at 08:57, brian br...@brianwhalen.net wrote: One of the users on my freebsd server that runs uw imap has an intermittent problem with inbox corruption. Is a fix planned? I see others have had this issue already. I am essentially seeing this https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=557103 though on Freebsd. Brian -- Dave Funk University of Iowa dbfunk (at) engineering.uiowa.eduCollege of Engineering 319/335-5751 FAX: 319/384-0549 1256 Seamans Center Sys_admin/Postmaster/cell_adminIowa City, IA 52242-1527 #include std_disclaimer.h Better is not better, 'standard' is better. B{ ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org