Oswald Buddenhagen writes:
Hi Oswald,
>> 2. Touch the MaildirStore's Path directories yourself.
>>
> that's the only reasonable option if you want to treat the path as a
> real thing - to mbsync it's simply a prefix (ok, that's not entirely
> true, but iirc that's only to avoid floods of repeti
On Wed, May 12, 2021 at 11:42:05PM +0200, Tassilo Horn wrote:
2. Touch the MaildirStore's Path directories yourself.
that's the only reasonable option if you want to treat the path as a
real thing - to mbsync it's simply a prefix (ok, that's not entirely
true, but iirc that's only to avoid fl
Oswald Buddenhagen writes:
Hi Oswald,
>>PS: I've attached my ~/.mbsyncrc just in case some of the observations
>>I've made are just caused by my configuration.
>
> they are.
>
>>Channel fastmail
>>SyncState *
>>
>>Channel gmail
>>
>>Channel shd
Ah, indeed, thanks for the pointer.
Back to my or
On Wed, May 12, 2021 at 06:51:03AM +0200, Tassilo Horn wrote:
PS: I've attached my ~/.mbsyncrc just in case some of the observations
I've made are just caused by my configuration.
they are.
Channel fastmail
SyncState *
Channel gmail
Channel shd
__
Hi all,
I use mbsync with great success together with mu/mu4e to read/write
mails. Mu is a maildir indexer. It has some option (lazy index
checking) for speeding up re-indexing which causes it to dive only into
directories if their MTIME has changed since the last indexing run.
Apparently, this
