David Bremner writes:
>> With a reused ssh connection this is sufficiently fast for me (<2s). If
>> there is interest I can clean up the script of hardcoded paths etc. and
>> put it on github.
>
> Sure, sounds at least as good as what I am using. Also, syncmaildir
> recently did something pretty
David Bremner writes:
>> With a reused ssh connection this is sufficiently fast for me (<2s). If
>> there is interest I can clean up the script of hardcoded paths etc. and
>> put it on github.
>
> Sure, sounds at least as good as what I am using. Also, syncmaildir
> recently did something pretty
David Mazieres writes:
> What happens if you get a message that's been stuck in a queue for a few
> days and has an old Date: header?
It would be missed. I have set the timespan to look backwards for new
mail to one month to be a bit safer against the stuck-in-queue cases,
but mails with older D
I have experimented with offlineimap, syncmaildir and rsync. The
append-only approach of notmuch makes synchronization of the mail corpus
simpler, so there are lots of options. With ssh access to the server, I
found rsync to be conceptually the simplest, but it turned out to be too
slow for me (w
David Mazieres writes:
> What happens if you get a message that's been stuck in a queue for a few
> days and has an old Date: header?
It would be missed. I have set the timespan to look backwards for new
mail to one month to be a bit safer against the stuck-in-queue cases,
but mails with older D
I have experimented with offlineimap, syncmaildir and rsync. The
append-only approach of notmuch makes synchronization of the mail corpus
simpler, so there are lots of options. With ssh access to the server, I
found rsync to be conceptually the simplest, but it turned out to be too
slow for me (w
