On Thu, Mar 02, 2017 at 09:05:00AM +0100, Oswald Buddenhagen wrote:
> On Thu, Mar 02, 2017 at 06:43:22AM +0000, Jos van den Oever wrote:
> > propagating new messages
> > >>> 5 APPEND "INBOX" (\Seen \Deleted) "30-Jun-2016 08:40:53 +0200" {8355}
> > + send literal data
> > (1 in progress) >>> 6 APPEND "INBOX" (\Deleted) "30-Jun-2016 08:40:53
> > +0200"
> > {9806}
> > Socket error from _____._______.nl (__.___.___.___:993): Connection reset
> > by peer
> >
> this definitely indicates a sequencing bug in mbsync
>
actually, i misread the log. the next command is sent only after the
command continuation request, so everything seems right (you can verify
that with -DN when using the 1.2 branch).
is this always happening with the same message?
take the {8355} as a hint, verify with -Ds.
if the problem is the message's content, -DN will help with that, too.
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________
isync-devel mailing list
isync-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/isync-devel
