From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from [192.168.1.7] ([108.95.88.138]) by ewsd; Mon Sep 17 09:28:45 EDT 2018 From: Stanley Lieber Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (1.0) Date: Mon, 17 Sep 2018 09:28:43 -0400 Subject: upas/imap4d vs ios mail.app Message-Id: <34730C0A-0134-459E-B8A2-DE994CFB1DF7@stanleylieber.com> To: 9front@9front.org X-Mailer: iPhone Mail (15G77) List-ID: <9front.9front.org> List-Help: X-Glyph: ➈ X-Bullshit: scale-out compliant SSL realtime cache extension at some point in the recent past trying to delete messages in ios mail.app c= onnecting to upas/imap4d started to fail almost all of the time. it looks li= ke mbox.idx is getting corrupted somehow (upas/fs running on the host compla= ins of such; note: manipulating messages via nedmail and upas/fs still works= , and updating the mbox via this method seems to repair [?] the mbox.idx eno= ugh that upas/fs stops complaining). ios mail.app simply complains that the m= essage could not be moved to Trash and then begins behaving strangely as its= internal database attempts to reconcile having deleted a message that is st= ill present on the server. i believe something is going wrong when upas/imap4d [magic] and causes mbox.= idx to be changed, but i don=E2=80=99t know how this part works and i have n= ot yet had a chance to investigate. anyone else seen this? sl