Skip to content

Conversation

@nicodh
Copy link
Member

@nicodh nicodh commented Nov 5, 2025

resolves #5648

Needs local core from chatmail/core#7348

Be aware not to use with existings accounts see #5648 (comment)

@nicodh nicodh force-pushed the add-multitransport branch from 572ba3c to 3590028 Compare November 5, 2025 11:02
@nicodh nicodh changed the title Add multitransport feat: add multitransport Nov 5, 2025
@nicodh nicodh added the new-core involves or requires an core update label Nov 5, 2025
'configured_addr',
transport.addr
)
await BackendRemote.rpc.stopIo(accountId)
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

These manual stopIo and startIo calls should not be needed anymore, the core now does this when configured_addr is set.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just pulled the latest state of the core multitransport PR. When I now add a new transport I see a lot of events in the logs and they don't stop any more:

121.6s [i]core/event: 2 src/imap.rs:778: 0 mails read from "INBOX".
121.6s [i]core/event: 2 src/imap/select_folder.rs:248: uid/validity change folder INBOX: new 1/1762373735 previous 3/1762373687.
121.6s [i]core/event: 2 src/imap/select_folder.rs:248: uid/validity change folder INBOX: new 3/1762373687 previous 1/1762373735.
121.6s [D]core/event: 2 ConnectivityChanged { kind: 'ConnectivityChanged' }
121.6s [D]core/event: 2 ImapInboxIdle { kind: 'ImapInboxIdle' }
121.6s [i]core/event: 2 src/scheduler.rs:685: IMAP session in folder "INBOX" supports IDLE, using it.
121.6s [i]core/event: 2 src/imap/select_folder.rs:248: uid/validity change folder INBOX: new 1/1762373735 previous 3/1762373687.
121.6s [i]core/event: 2 src/imap/idle.rs:39: Skipping IDLE in "INBOX" because there may be new mail.
121.6s [i]core/event: 2 src/scheduler.rs:425: IMAP loop iteration for inbox finished, keeping the session.
121.6s [i]core/event: 2 src/imap.rs:881: resync_folder_uids: Collected 0 message IDs in INBOX.
121.6s [i]core/event: 2 src/imap/select_folder.rs:248: uid/validity change folder INBOX: new 3/1762373687 previous 1/1762373735.
121.6s [i]core/event: 2 src/imap.rs:585: fetch_new_msg_batch(INBOX): UIDVALIDITY=1762373687, UIDNEXT=3.
121.6s [i]core/event: 2 src/imap/select_folder.rs:248: uid/validity change folder INBOX: new 1/1762373735 previous 3/1762373687.
121.6s [i]core/event: 2 src/imap.rs:778: 0 mails read from "INBOX".
121.6s [i]core/event: 2 src/imap/select_folder.rs:248: uid/validity change folder INBOX: new 3/1762373687 previous 1/1762373735.
121.6s [i]core/event: 2 src/imap.rs:881: resync_folder_uids: Collected 0 message IDs in INBOX.
121.6s [i]core/event: 2 src/imap/select_folder.rs:248: uid/validity change folder INBOX: new 1/1762373735 previous 3/1762373687.
121.6s [i]core/event: 2 src/imap.rs:585: fetch_new_msg_batch(INBOX): UIDVALIDITY=1762373735, UIDNEXT=1.

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It is broken by the latest WIP commit chatmail/core@37a6304, the branch is not usable at the moment.

But once it is working stop_io and start_io will not be necessary.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

new-core involves or requires an core update

Projects

None yet

Development

Successfully merging this pull request may close these issues.

list, remove and add transports

3 participants