Re: [Evolution] Interaction with ProtonMail “Error syncing changes: mailbox 4 does not exist”



On Tue, 2020-05-26 at 12:37 +0000, Dan Kortschak wrote:
On Tue, 2020-05-26 at 08:44 +0200, Milan Crha via evolution-list
wrote:
On Tue, 2020-05-26 at 04:34 +0200, Dan Kortschak via evolution-list
wrote:
This problem is only fixed by quiting evolution and killing
evolution-source-registry, and going to the ProtonMail web client
and
emptying the trash.

    Hi,
why also the evolution-source-registry? I'd not expect that to
change
anything.

I intend to instrument the ProtonMail bridge application, but I
would
like to have a basic idea of what it is that I should be looking
for
before I jump into that.

You can see what it does in the background when you start Evolution
from a terminal as this:

   $ CAMEL_DEBUG=imapx:io evolution

which logs raw communication between the server and Evolution.
Whether
it'll help you to diagnose the problem I'm not sure.
    Bye,
    Milan


Thanks for both of those. I have retried without killing the source
registry and it is resolved without that.

The relevant output from CAMEL_DEBUG=imapx:io is as follows:

[imapx:A] I/O: 'A00133 UID STORE 338 -FLAGS.SILENT (\DELETED)'
[imapx:A] I/O: 'A00133 OK UID STORE completed'
[imapx:A] I/O: 'A00134 UID STORE 338 -FLAGS.SILENT (JUNK)'
[imapx:A] I/O: 'A00134 NO mailbox 4 does not exist'
[imapx:A] I/O: 'A00135 UID STORE 338 -FLAGS.SILENT (\DELETED)'
[imapx:A] I/O: 'A00135 OK UID STORE completed'
[imapx:A] I/O: 'A00136 UID STORE 338 -FLAGS.SILENT (JUNK)'
[imapx:A] I/O: 'A00136 NO mailbox 4 does not exist'
[imapx:A] I/O: 'A00137 STATUS INBOX (MESSAGES UNSEEN UIDVALIDITY
UIDNEXT)'
[imapx:A] I/O: '* STATUS INBOX (UIDVALIDITY 4 UIDNEXT xxxx MESSAGES
xxxx UNSEEN xx)'
[imapx:A] I/O: 'A00137 OK STATUS completed'

Can you point me to documentation where I can read about how to
interpret this?

thanks
Dan Kortschak


I think that I just caught the trigger in action. I just saw a mail get
sent to junk (ProtonMail server-side filter) and then this

[imapx:A] I/O: 'A00170 UID MOVE 3533 Spam'
[imapx:A] I/O: '* 3177 FETCH (FLAGS ($junk junk) UID 3533)'
[imapx:A] I/O: '* 3177 EXISTS'
[imapx:A] I/O: '* OK [UNSEEN 3] '
[imapx:A] I/O: 'A00170 NO Label does not exist'
[imapx:A] I/O: 'A00171 STATUS Trash (MESSAGES UNSEEN UIDVALIDITY
UIDNEXT)'
[imapx:A] I/O: '* STATUS Trash (MESSAGES 0 UNSEEN 0 UIDVALIDITY 4
UIDNEXT 349)'
[imapx:A] I/O: 'A00171 OK STATUS completed'

and then the same kind of issue as above. This may be enough for me to
be able to give ProtonMail enough information for them to reproduce
locally (which they have not been able to do before).

ProtonMail uses labels rather than real IMAP folders on their servers,
so perhaps the bridge is causing some confusion in the junk/trash
labelling (their junk and trash folders as presented by evolution allow
per mail deletion, unlike real IMAP servers that I connect to so that
seem to be behaving differently).

Having docs to read to understand this better will still help me
though.

thanks
Dan Kortschak




[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]