Re: Suddenly errors regarding "near side box INBOX/XXX cannot be opened."

[Johannes K. <ma...@oj...>]

Hi all,

On 04.12.24 06:43 Johannes Kastl wrote:
> Hi Oswald,
> 
> On 02.12.24 11:28 Oswald Buddenhagen via isync-devel wrote:
>> On Sun, Dec 01, 2024 at 08:47:48PM +0100, Johannes Kastl wrote:
>>>> Error: channel YYY: near side box INBOX/XXX cannot be opened.
>>>
>>>Funnily enough, in one case this happened after the folder was created
>>>locally and the sync succeeded. On the next run the error above was shown.
>>>
>> weird. try 'mbsync -ls' for starters.
>> if that looks good, try 'mbsync -l'.
>> if that still looks good, it's presumably not a user error.
>> in that case try syncing only one failing mailbox (YYY:INBOX/XXX).
>> add -D to the above command and the normal YYY run, und mail me the
>> logs.
> 
> Will try to do some more debugging.

Hmmm, I find no obvious errors (at least, obvious to me...):

> Opening far side box INBOX/20140102_BACKUP...
> F: [ 10] Enter open_box
> F: >>> 7 SELECT "INBOX/20140102_BACKUP"^M
> F: [ 10] Leave open_box 
> Opening near side box INBOX/20140102_BACKUP...
> F: [ 7] Callback leave load_box
> F: * 97 EXISTS
> F: * 0 RECENT 
> F: * FLAGS (\Answered \Flagged \Deleted \Seen \Draft)
> F: * OK [PERMANENTFLAGS (\Answered \Flagged \Draft \Deleted \Seen \*)] Unlimited
> F: * OK [UIDNEXT 1396] Predicted next UID
> F: * OK [UIDVALIDITY 1388669892] UIDs valid
> F: 7 OK [READ-WRITE] SELECT completed
> F: [ 10] Callback enter open_box, sts=0, uidvalidity=1388669892
> Error: channel XXX: near side box INBOX/20140102_BACKUP cannot be opened.
> F: Called get_caps, ret=0x7
> N: Called get_caps, ret=0

And the same for all children of this folder.

I can send the log directly, if it is any help?

Kind Regards,
Johannes