You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
However, nobody sets the connectivity to connected for the whole fake idle duration, so most of the time "connecting" is displayed.
For a fix it should be sufficient to set the status to connected at the end of connect. For testing we probably need an option to disable use of IDLE and maybe even add it to developer options on desktop.
When the server does not support IDLE, core takes the following path at the end of synchronizing seen flags:
deltachat-core-rust/src/scheduler.rs
Lines 563 to 575 in a119b24
Connectivity is set to "Connected", then we go into
fake_idle
.Normal
idle
does not changeconnectivity
, whilefake_idle
callsprepare
here:deltachat-core-rust/src/imap/idle.rs
Lines 158 to 164 in a119b24
prepare
callsconnect
which in turn changes the connectivity toconnecting
:deltachat-core-rust/src/imap.rs
Line 305 in a119b24
However, nobody sets the connectivity to
connected
for the whole fake idle duration, so most of the time "connecting" is displayed.For a fix it should be sufficient to set the status to
connected
at the end ofconnect
. For testing we probably need an option to disable use of IDLE and maybe even add it to developer options on desktop.163.com does not support IDLE.
Forum thread: https://support.delta.chat/t/cannot-connect-to-the-inbox-after-logging-into-163-mailbox/2756
The text was updated successfully, but these errors were encountered: