From: ori@eigenstate.org
To: 9front@9front.org
Subject: Re: [9front] upas/fs: handle outlook's quirks
Date: Sat, 09 Oct 2021 10:22:55 -0400 [thread overview]
Message-ID: <DD690A6FEB2FD9B474D01D55E22CF479@eigenstate.org> (raw)
In-Reply-To: <405ABA392F41295D7D6361D94B2A8E08@gmx.com>
Quoth risto.salminen@gmx.com:
> The handling of a message larger than expected works
> exactly in the same way as the current quirk for Gmail.
> When requesting the last chunk of a message, upas/fs
> increases the chunk length, so that hopefully the whole
> message will be read, and then afterwards also adjusts
> its internal notion of the message length accordingly.
>
> To benefit from this patch, the desired mailbox indices
> have to be recreated, by manually removing them, so that
> upas/fs will then create them automatically. Otherwise,
> things will continue to work as before.
>
> Would this be useful for the broader audience?
Yes, though I'm probably going to see if I can
make sense of some other imap implementations and
see how fetching is handled differently there before
I commit this.
Give me a couple of days.
next prev parent reply other threads:[~2021-10-09 14:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-09 10:36 risto.salminen
2021-10-09 14:22 ` ori [this message]
2021-10-12 7:28 ` Risto Salminen
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=DD690A6FEB2FD9B474D01D55E22CF479@eigenstate.org \
--to=ori@eigenstate.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).