Re: inbox corruption by iphone

  This message is in MIME format.  The first part should be readable text,
  while the remaining parts are likely unreadable without MIME-aware tools.

--0-969105492-1438441192=:43156
Content-Type: TEXT/PLAIN; charset=utf-8; format=flowed
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by mxout24.cac.washington.edu id t71F03bc010920

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=20
mailbox (such as MIX) instead of the traditional mbox. Of course this=20
won't work in an environment that requires local direct access to the=20
mailbox by non-C-client aware mail clients. If you can switch to MIX=20
format there are many advantages (performance, scale-ability, backup=20
facilitation, etc).
However if you do switch to MIX be -sure- to run the Panda distro, there=20
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=20
which he called "Panda" and then started developing a commercial product=20
from there.

He kept Panda alive and semi-open sourced, making bug-fixes and adding=20
some small improvements (I know from conversations I had with him in '09=20
about a UW-imap bug I found/fixed ). He made it available to people who=20
explicitly asked him for it.

After his death people took the last known version of Panda and turned it=
=20
into a github project and made additional improvements to it (I=20
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=20
>> accounts for around 12 years. We are all Mac/iOS users: we noted early=
 on=20
>> that UW_IMAP doesn't cope well with more than one client logged into a=
n=20
>> account at the same time. When the most any of us had was two machines=
=20
>> (home/office or home/laptop) that was relatively easy to manage but wh=
en=20
>> iOS came along(iPhones, iPads) came along things began to unravel and =
the=20
>> situation became unworkable. iPhones never stayed in sync with the ser=
ver,=20
>> though I have not seen the specific corruption you mention.
>>=20
>> I am now in the process of transferring family accounts to Fastmail an=
d am=20
>> setting up Dovecot on Linode/Ubuntu for a few other accounts I manage.=
=20
>> Sadly, UW_IPAD=E2=80=99s future died with Mark Crispin.
>>=20
>> C
>> ________________________
>>=20
>>=20
>>> On 22 Jul 2015, at 08:57, brian <[email protected]> wrote:
>>>=20
>>> One of the users on my freebsd server that runs uw imap has an=20
>>> intermittent problem with inbox corruption. Is a fix planned? I see o=
thers=20
>>> have had this issue already. I am essentially seeing this=20
>>> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=3D557103 though on=20
>>> Freebsd.
>>>=20
>>>=20
>>> Brian

--=20
Dave Funk                                  University of Iowa
<dbfunk (at) engineering.uiowa.edu>        College of Engineering
319/335-5751   FAX: 319/384-0549           1256 Seamans Center
Sys_admin/Postmaster/cell_admin            Iowa City, IA 52242-1527
#include <std_disclaimer.h>
Better is not better, 'standard' is better. B{
--0-969105492-1438441192=:43156
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

_______________________________________________
Imap-uw mailing list
[email protected]
http://mailman13.u.washington.edu/mailman/listinfo/imap-uw

--0-969105492-1438441192=:43156--