From: Stanley Lieber <sl@stanleylieber.com>
To: 9front@9front.org
Subject: upas/imap4d vs ios mail.app
Date: Mon, 17 Sep 2018 09:28:43 -0400 [thread overview]
Message-ID: <34730C0A-0134-459E-B8A2-DE994CFB1DF7@stanleylieber.com> (raw)
at some point in the recent past trying to delete messages in ios mail.app connecting to upas/imap4d started to fail almost all of the time. it looks like mbox.idx is getting corrupted somehow (upas/fs running on the host complains 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 enough that upas/fs stops complaining). ios mail.app simply complains that the message could not be moved to Trash and then begins behaving strangely as its internal database attempts to reconcile having deleted a message that is still present on the server.
i believe something is going wrong when upas/imap4d [magic] and causes mbox.idx to be changed, but i don’t know how this part works and i have not yet had a chance to investigate.
anyone else seen this?
sl
reply other threads:[~2018-09-17 13:28 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=34730C0A-0134-459E-B8A2-DE994CFB1DF7@stanleylieber.com \
--to=sl@stanleylieber.com \
--cc=9front@9front.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).