From: Kurt H Maier <khm@sciops.net>
To: 9front@9front.org
Subject: Re: [9front] upas/fs imap fetch failed
Date: Thu, 22 Oct 2020 13:52:36 -0700 [thread overview]
Message-ID: <20201022205236.GA1322@wopr> (raw)
In-Reply-To: <79F978E0107BCB66D74518321178DD41@sdf.org>
On Thu, Oct 22, 2020 at 09:20:36PM +0100, nicolagi@sdf.org wrote:
> parseattachments 42d380 5350 bonudary --000000000000a53d3b05b2093efc
I pushed a fix for this typo ("bonudary") but of course it is not the
problem.
> upas/fs: imap: fetchrsp: read: tls hungup
Something is getting disconnected. Do you know what?
khm
next prev parent reply other threads:[~2020-10-22 20:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-22 20:20 nicolagi
2020-10-22 20:52 ` Kurt H Maier [this message]
2020-10-23 7:05 ` [9front] " nicolagi
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=20201022205236.GA1322@wopr \
--to=khm@sciops.net \
--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).