isync-devel

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

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

Dear all,

today I noticed that some of my mbsync calls are returning errors.

> 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.

The command I am using is:

mbsync --pull -c ~/.config/mbsync/YYY.conf YYY

The configuration was only changed recently to replace SSLType with
TLSType and remove the TLSVersions I had previously. But after that it
was already working properly.

I do not see any obvious permission issues in the file system.

Side note:
I also noticed that my GMX mailboxes suddenly stop using Entw&rfe
locally, but use the proper German "Entwürfe". I am not sure if this
is related or something that has changed on the provider's side?

Did anyone experience something similar? Is this a known issue that I
overlooked?

I'll do some more digging and debugging in the next couple of days,
once I find time.

Have a nice day!

Kind Regards,
Johannes

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

[Oswald B. <osw...@gm...>]

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.

>I also noticed that my GMX mailboxes suddenly stop using Entw&rfe
>locally, but use the proper German "Entwürfe". I am not sure if this
>is related or something that has changed on the provider's side?
>
v1.5 gained proper support for UTF-7 & UTF-8, so your pre-existing local
folders need to be renamed.
it's possible that this is in fact the root cause of the above problem,
but that depends on your exact config.

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

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

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.

>>I also noticed that my GMX mailboxes suddenly stop using Entw&rfe
>>locally, but use the proper German "Entwürfe". I am not sure if this
>>is related or something that has changed on the provider's side?
>>
> v1.5 gained proper support for UTF-7 & UTF-8, so your pre-existing local
> folders need to be renamed.
> it's possible that this is in fact the root cause of the above problem,
> but that depends on your exact config.

Only the name of the drafts folder changed, the folder that cannot be
synced have not changed and still have the same name.

Kind Regards,
Johannes

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

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

[Oswald B. <osw...@gm...>]

On Sun, Dec 08, 2024 at 09:23:11AM +0100, Johannes Kastl wrote:
>> Error: channel XXX: near side box INBOX/20140102_BACKUP cannot be opened.
>
>I can send the log directly, if it is any help?
>
yes, but let's go for the complete set:
- your config file
- cd <local Path>; find -type d
- mbsync -D -ls
- mbsync -D -l <channel>
- mbsync -D <channel>