On Thu, Oct 27, 2022 at 07:27:22PM +0200, laalsaas wrote:
I wanted to kindly ask
whether there is anything holding you back from releasing 1.5.
yes, there are two known regressions, one of which isn't properly
investigated yet.
additionally, the SASL license issue isn't fully resolved yet due t
Hi,
I've been using mbsync for some time now, and every year or so I'm faced with
messages like:
Warning: lost track of 104 pulled message(s)
Warning: lost track of 1 pushed message(s)
Searching the internet, lots of other people have enountered this, and as far
as I can see, the general advice
On Fri, Oct 28, 2022 at 10:15:51AM +0100, Edd Barrett wrote:
I've been using mbsync for some time now, and every year or so I'm
faced with messages like:
Warning: lost track of 104 pulled message(s)
Warning: lost track of 1 pushed message(s)
Searching the internet, lots of other people have en
Hi,
On Fri, Oct 28, 2022 at 02:23:48PM +0200, Oswald Buddenhagen wrote:
> > Problem is, the message doesn't go away when you re-run mbsync.
> >
> that's worrisome.
> re-run with -D.
I'm not sure how much context you need. I'm hesitant to post the whole log as
it contains things about my mailboxe
On Fri, Oct 28, 2022 at 03:32:44PM +0100, Edd Barrett wrote:
I'm not sure how much context you need. I'm hesitant to post the whole
log as
it contains things about my mailboxes in it.
i need the full log. in fact, of two consecutive runs, as this is an
inter-run problem. you can limit it on th
