On Thu, Mar 02, 2017 at 06:43:22AM +, 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 fro
Thanks for the explanation. I'll have a look at using PipelineDepth 1.
My use case is actually to modify a subset of all my mails and re-upload them.
Perhaps isync is too heavy a tool for this and I should script with some imap
lib.
Basically, I'm doing:
mbsync -V --config mbsyncrc --pull MAIL
On Thu, Mar 02, 2017 at 03:23:50PM +, Jos van den Oever wrote:
> My use case is actually to modify a subset of all my mails and
> re-upload them. Perhaps isync is too heavy a tool for this and I
> should script with some imap lib.
>
the only more lightweight solution i can think of would be u
On Thursday 02 March 2017 18:55:20 Oswald Buddenhagen wrote:
> i hope "modify" includes renaming them (at least throwing away the
> ,U=NNN part), as otherwise mbsync won't re-upload anything.
Yes, modify means: for all mails from a certain address that have a forwarded
mail as attachment, add the
