Result of bisect:
859b7dd7f2dc5d8396488700e0ab35d207188ed9 is the first bad commit
commit 859b7dd7f2dc5d8396488700e0ab35d207188ed9
Author: Oswald Buddenhagen
Date: Thu Jun 9 13:32:16 2022 +0200
try to avoid extra syscalls when reading sockets
so far we shifted down the buffered data o
On Wed Jan 10, 2024 at 12:22, Oswald Buddenhagen via isync-devel
wrote:
> this doesn't look like a data incompatibility, so clearing won't do
> anything useful.
> try running with -D to see whether it's doing something obviously
> stupid. the next level would be strace'ing it.
> anyway, my firs
On Wed, Jan 10, 2024 at 09:59:07AM +0100, Bence Ferdinandy wrote:
On Thu Aug 17, 2023 at 14:45, Oswald Buddenhagen
wrote:
On Thu, Aug 17, 2023 at 07:59:09AM -0400, brittanderson--- via isync-devel
wrote:
>The error has reoccured. It is:
>
>Socket error: receive buffer full. Probably protocol
Hi all,
On Thu Aug 17, 2023 at 14:45, Oswald Buddenhagen
wrote:
> On Thu, Aug 17, 2023 at 07:59:09AM -0400, brittanderson--- via isync-devel
> wrote:
> >The error has reoccured. It is:
> >
> >Socket error: receive buffer full. Probably protocol error.
I also ran into this error with davmail.
On Fri, Aug 18, 2023 at 08:37:52AM -0400, brittanderson--- via isync-devel
wrote:
Thank you for the follow-up. I just had another message that provoked
this error. This one from protonmail, so it is not a microsoft exchange
specific issues, and I do not use davmail for the protonmail account.
Thank you for the follow-up. I just had another message that provoked
this error. This one from protonmail, so it is not a microsoft exchange
specific issues, and I do not use davmail for the protonmail account.
I did notice that this email had 12 (twelve) embedded images. Perhaps
this is somehow
On Thu, Aug 17, 2023 at 07:59:09AM -0400, brittanderson--- via isync-devel
wrote:
The error has reoccured. It is:
Socket error: receive buffer full. Probably protocol error.
hmm, this might in fact be one of the two regressions that prevent me
from releasing 1.5.0 - i honestly don't remember,
The error has reoccured. It is:
Socket error: receive buffer full. Probably protocol error.
running =mbsync -D university=
Gives an output that includes this snippet:
#+Begin_quote
N: Called get_uidnext, ret=1273
-> log: F 1 1273 (save UIDNEXT of near side)
-> log: # 192877 0 yMXnDcoTZKtm (new
On Tue, Aug 15, 2023 at 02:31:11PM -0400, brittanderson--- via isync-devel
wrote:
Oswald Buddenhagen writes:
the two sides have different uids. the ones appearing in the imap
stream don't match the local mailboxes. the complete output contains
the local (or more precisely, near-side) uids as w
Oswald Buddenhagen writes:
> which "fetch" issue in particular are you referring to?
IMAP error: bogus FETCH response
This is mentioned in several mails on the list, and I believe there is
one that says you have a fix in master, but were waiting to release
because of two regressions.
When I
On Tue, Aug 15, 2023 at 10:47:12AM -0400, Britt Anderson via isync-devel wrote:
Because of the "fetch" issue I upgraded from 1.4.4 to master,
which "fetch" issue in particular are you referring to?
which was been running well when I got a non-zero exit code because of
socket error with a stat
Because of the "fetch" issue I upgraded from 1.4.4 to master, which was
been running well when I got a non-zero exit code because of
socket error with a statement about a possible protocol violation. I
downgraded to 1.4.4 and the error went away. After awhile of dealing
with the "fetch" issue needi
12 matches
Mail list logo
