Re: 'Connection reset by peer'

[Oswald B. <osw...@gm...>]

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 when used without
the LITERAL+ extension; this is consistent with previous reports. there
must be something wrong with cmd_sendable() (of course there is - have
you seen it? :D) or the related code.

you can try PipelineDepth 1 as a workaround, but this will be obviously
even slower (though i suppose it could be ok if the latency to the
davmail server is low compared to that of the exchange connection).