On Mon, Jun 17, 2019 at 6:28 PM Luis Chamberlain wrote:
> I however use systemd timers / unit files instead of cronjobs to
> control and log my inbox proccessing.
I failed to mention, another justification for systemd unit timers is
how if you're starting fetching fresh, ie a new system, and you
I just moved from offlineimap over to mbsync and I'm pretty happy.
I however use systemd timers / unit files instead of cronjobs to
control and log my inbox proccessing. Instead of just keeping this
private figured I'd share it as it may be useful to others.
My respective fork for those who prefe
When availble, systemd unit files can be leveraged by users
to enable calling msync for you on a regular basis. This can also
be used to allow you to configure fetching mail at differnt
intervals for different configurations.
In order to use the systemd unit files a user must explicitly enable
and
If you're using gmail for development you may often have tons of
mailing lists for one project, and so may use nested labels. This
shows how to use them, and how to try to avoid goin over gmail's
quota.
---
src/mbsyncrc.sample | 42 ++
1 file changed, 42 ins
> > - 1.3.0-clean.log -> a sync with the old version
>
> > M: >>> 5 UID FETCH *:* (UID)
> > M: * 1 FETCH (UID 1)
> > M: * 2 FETCH (UID 2)
> > [...]
> > M: * 4448 FETCH (UID 75802)
> > M: * 4449 FETCH (UID 75803)
> > M: 5 OK UID FETCH done
>
> the somewhat nonsensical old command - some servers wo
On Sun, Jun 16, 2019 at 08:25:24PM +0200, Guillaume Brogi wrote:
> - 1.3.0-clean.log -> a sync with the old version
> M: >>> 5 UID FETCH *:* (UID)
> M: * 1 FETCH (UID 1)
> M: * 2 FETCH (UID 2)
> [...]
> M: * 4448 FETCH (UID 75802)
> M: * 4449 FETCH (UID 75803)
> M: 5 OK UID FETCH done
the somewha
