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 dm-list-email-notm...@scs.stanford.edu writes:
David Bremner da...@tethera.net writes:
Brian Sniffen bsnif...@akamai.com writes:
I'm thrilled by using notmuch to manage my mail. Low-latency search is
very important to me. But I use computers in a couple of
places---several
David Bremner da...@tethera.net 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
David Mazieres writes:
> David Bremner writes:
>
>> Brian Sniffen writes:
>>
>>> I'm thrilled by using notmuch to manage my mail. Low-latency search is
>>> very important to me. But I use computers in a couple of
>>> places---several of which are laptops. Has anyone stories to share of
>>>
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
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
Tilmann Singer writes:
> 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
Tilmann Singer 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
Tilmann Singer writes:
> The steps performed on a sync run are roughly like this:
>
> - local: notmuch new
> - local: notmuch search --output=messages ..
> - remote: notmuch new
> - remote: notmuch search --output=messages ..
> - compare search results
> - run rsync for mails that only exist
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
Tilmann Singer t...@tils.net 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
Tilmann Singer t...@tils.net writes:
The steps performed on a sync run are roughly like this:
- local: notmuch new
- local: notmuch search --output=messages some time ago..now
- remote: notmuch new
- remote: notmuch search --output=messages some time ago..now
- compare search results
-
David Mazieres dm-list-email-notm...@scs.stanford.edu 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
Tilmann Singer t...@tils.net writes:
David Mazieres dm-list-email-notm...@scs.stanford.edu 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
David Bremner writes:
> Brian Sniffen writes:
>
>> I'm thrilled by using notmuch to manage my mail. Low-latency search is
>> very important to me. But I use computers in a couple of
>> places---several of which are laptops. Has anyone stories to share of
>> successful multi-computer notmuch
Brian Sniffen writes:
> I'm thrilled by using notmuch to manage my mail. Low-latency search is
> very important to me. But I use computers in a couple of
> places---several of which are laptops. Has anyone stories to share of
> successful multi-computer notmuch sync, for a corpus of a
>
I'm thrilled by using notmuch to manage my mail. Low-latency search is
very important to me. But I use computers in a couple of
places---several of which are laptops. Has anyone stories to share of
successful multi-computer notmuch sync, for a corpus of a
quarter-million messages or so?
I've
Brian Sniffen bsnif...@akamai.com writes:
I'm thrilled by using notmuch to manage my mail. Low-latency search is
very important to me. But I use computers in a couple of
places---several of which are laptops. Has anyone stories to share of
successful multi-computer notmuch sync, for a
I'm thrilled by using notmuch to manage my mail. Low-latency search is
very important to me. But I use computers in a couple of
places---several of which are laptops. Has anyone stories to share of
successful multi-computer notmuch sync, for a corpus of a
quarter-million messages or so?
I've
19 matches
Mail list logo