On Sun, 15 May 2022, at 7:49 PM, Oswald Buddenhagen wrote:
> On Sun, May 15, 2022 at 12:30:20PM +0100, Sean Hammond wrote:
>>Not segfaults, no. isync just exits with a non-zero exit status and
>>without having synced all the mailboxes and messages. For example:
>> [...]
>>
> ok, that's within
On Sun, May 15, 2022 at 12:30:20PM +0100, Sean Hammond wrote:
Not segfaults, no. isync just exits with a non-zero exit status and
without having synced all the mailboxes and messages. For example:
[...]
ok, that's within expectations. such huge mailboxes always cause
trouble, because gmail
On Sun, 15 May 2022, at 12:11 PM, Oswald Buddenhagen wrote:
> On Sun, May 15, 2022 at 11:55:43AM +0100, Sean Hammond wrote:
>>With Gmail I still get a variety of errors and warnings some of which
>>cause isync to crash, [...]
>>
> do you mean actual crashes, like segfaults? in this case i'd like
On Sun, May 15, 2022 at 11:55:43AM +0100, Sean Hammond wrote:
With Gmail I still get a variety of errors and warnings some of which
cause isync to crash, [...]
do you mean actual crashes, like segfaults? in this case i'd like to
know details.
if you feel like it, you can try the
On Fri, 27 Aug 2021, at 6:06 PM, Oswald Buddenhagen wrote:
> - i presume you're not using v1.4 yet, as otherwise you'd be getting
>warnings about the master/slave keywords. the exceedingly large "lost
>track of" number despite PipelineDepth 1 also suggests this (the
>counting simply
