From: sirjofri <sirjofri+ml-9front@sirjofri.de>
To: 9front@9front.org
Subject: Re: [9front] Incoming mails disappearing
Date: Thu, 28 Apr 2022 15:50:00 +0000 (UTC) [thread overview]
Message-ID: <e5099bc1-0203-4032-a90f-8743a932236c@sirjofri.de> (raw)
In-Reply-To: <32E64D93BDFA3777BF37AB3895FEC813@eigenstate.org>
28.04.2022 16:27:49 ori@eigenstate.org:
> The only thing I can think of here is an imap bug or a pipe
> bug. What happens if you put a log message and early return
> here:
>
> /sys/src/cmd/upas/imap4d/mbox.c:464: deletemsg(Box *box, Msgset
> *ms)
I will try that. It's always hard to test things that work most of the
time and only occasionally fail.
I'll report back. It can take a day or so since I only have two daily
mails that almost reliably fail.
sirjofri
next prev parent reply other threads:[~2022-04-28 15:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-28 13:09 sirjofri
2022-04-28 14:27 ` ori
2022-04-28 15:50 ` sirjofri [this message]
2022-05-29 16:38 ` sirjofri
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=e5099bc1-0203-4032-a90f-8743a932236c@sirjofri.de \
--to=sirjofri+ml-9front@sirjofri.de \
--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).