From: nicolagi@sdf.org
To: 9front@9front.org
Subject: Re: [9front] upas/fs imap fetch failed
Date: Fri, 23 Oct 2020 08:05:53 +0100 [thread overview]
Message-ID: <7A1325C96275F1E2919974762BE7F001@sdf.org> (raw)
In-Reply-To: <20201022205236.GA1322@wopr>
> 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 wha
Hmm. I'm not sure this is a symptom or a cause.
I don't know if you'll agree with my thoughts:
Seeing that fetchrsp's job seems to be parsing a response from the
server, I thought maybe there was a problem parsing one of the
responses, and that sent the server into a bad state, unable to parse
further responses. To put this theory to the test, I went in and
deleted the attachment delimited by --000000000000a53d3b05b2093efc
(with mutt) and started upas/fs again. Now I see all mail. (BUT:
Also note how your e-mail text was clipped. It wasn't me. "bad
chars" and "reducing size" seem to be good hints.)
When this happens again, what's the best way to step through the
response parsing? On another system I would perhaps capture the
packets and look at them and at fetchrsp() at the same time, but I
don't know if that can be done here. And I'm sure there are smarter
ways. :-)
Thank you
prev parent reply other threads:[~2020-10-23 7:05 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 ` [9front] " Kurt H Maier
2020-10-23 7:05 ` nicolagi [this message]
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=7A1325C96275F1E2919974762BE7F001@sdf.org \
--to=nicolagi@sdf.org \
--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).