Sorry if this question is answered somewhere, but I'm wondering: What
is the best way to enable and disable maildir.synchronize_flags?
It seems that disabling it should simply be safe. But re-enabling, one
risks losing tags, as the next notmuch new will cause old maildir flags
to override the
I've been running into this issue lately where I agree to meet people
and we say it's confirmed, but if don't send them a calendar invite of
mime type text/calendar, then it's as if we never agreed and they don't
show up. I get, "Oh, you never sent me a calendar invite so it wasn't
in my
Jani Nikula writes:
> It's not going to help you, but I'll mention a few of the issues the old
> folder: search had, which we also had complaints about, and which would
> have been quite hard to fix while preserving the behaviour you want. In
> short, we considered the old folder: search broken.
Jani Nikula writes:
> On Fri, 02 May 2014, dm-list-email-notmuch at scs.stanford.edu wrote:
>>
>> I'm using a pretty standard maildir++ layout. For example, underneath
>> my database.path I have a bunch of mail in directories such as:
>>
>> .INBOX.Main/{new,cur}
>> .mail.class/{new,cur}
Hey, I'm playing around with the head of the git repository
(bc64cdce289d84be2550c4fccb1f008d15eaeb0e) to try to figure out how the
new folder: prefixes work, as folders are a critical part of how I
organize my mail. (Since tags are not hierarchical, folders are the
best way for me to group mail
Austin Clements writes:
>> A middle ground might be to use the maximum of two values: 1) the
>> time-of-day at which notmuch started executing, and 2) the highest ctime
>> in the database plus 100 microseconds (leaving plenty of slop to store
>> timestamps as IEEE doubles with 52 significant
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
David Bremner writes:
>> Exactly. It could be a tick, or just the current time of day if your
>> clock does not go backwards. (I'd be willing to do a full scan if the
>> clock ever goes backwards.) The advantage of time is that you don't
>> have to synchronously update some counter.
>
> I
Gaute Hope writes:
>> A better approach would be to add a new "modtime" xapian value that is
>> updated whenever the tags or any other terms (such as XFDIRENTRY) are
>> added to or deleted from a docid. If it's a Xapian value, rather than a
>> term, then modtime will be queriable just like
At Tue, 25 Jan 2011 10:08:12 +1030,
Tim Stoakes wrote:
>
> I do something like this by using some shell scripts with formail, to
> 'store' notmuch tags into the X-Label headers of the individual mails.
> Offlineimap then syncs these headers. If I need the tags to become
> notmuch-ified on the
One of the features I would like to see from notmuch is an easier
ability to synchronize tags across machines. At the very least, I
would need either incremental dump and restore, or some way to
communicate arbitrary tags to a local imap server that shares
notmuch's maildir (much as notmuch
11 matches
Mail list logo
