Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

IMAP flag updates are sometimes not synced #469

Open
jknockaert opened this issue Mar 22, 2024 · 6 comments
Open

IMAP flag updates are sometimes not synced #469

jknockaert opened this issue Mar 22, 2024 · 6 comments
Labels
can't repoduce The issue can't be reproduced

Comments

@jknockaert
Copy link

I noticed that with recent versions of Bridge (since 3.9 or earlier) sometimes message IMAP flag updates (\Seen, \Flagged etc) are not properly synced. I couldn't exactly figure out what triggers the issue, but it seems to happen in a setup where one Bridge installation is already synced and a second Bridge installation is syncing the same account. If a flag is changed using the first installation (e.g. messages marked as read) while the second installation is in the process of syncing, the second installation will never pick up the flag change.

Am using Bridge on macOS.

@LBeernaertProton
Copy link
Collaborator

Hey @jknockaert , this is currently expected. While syncing we only allow certain events to be applied. Once the sync process completes the mail state will catch up.

@jknockaert
Copy link
Author

@LBeernaertProton The problem seems to be that (in some cases) the second installation never catches up on the flag updates applied through the first installation while the second installation was in the process of syncing.

@LBeernaertProton
Copy link
Collaborator

Could you share the logs of the second machine? It would be great if it captures the whole syncing process and a couple of min after the sync has completed.

@jknockaert
Copy link
Author

OK will try to post the logs next time this happens.

@LBeernaertProton
Copy link
Collaborator

We were unable to reproduce this locally.

@LBeernaertProton LBeernaertProton added the can't repoduce The issue can't be reproduced label Mar 26, 2024
@jknockaert
Copy link
Author

Yesterday again I noticed that on one installation (of Bridge) a message was synced as "unread" whereas it was marked as read in all other installations (bridge and native apps). This didn't update automatically. Then when I today marked it as "read" in the first installation (in order to sync it manually) the instance of Bridge crashed. Unfortunately nothing of any use in the logs.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
can't repoduce The issue can't be reproduced
Projects
None yet
Development

No branches or pull requests

2 participants