nextcloud / nextcloud/mail

Duplicate message sync on every sync run

Open
#11,054 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

1. to develop bug performance 🚀
Dominant language
JavaScript
Stars
1k
Forks
348
Avg merge
12h 28m
Merged PRs (30d)
91

Description

Steps to reproduce
  1. Sync a mailbox and watch the imap log
Expected behavior

Either SELECT or EXAMINE should be used not both.

Actual behavior

Mail app double polls mail server with both the EXAMINE and SELECT command

Mail app version

No response

Nextcloud version

No response

Mailserver or service

No response

Operating system

No response

PHP engine version

None

Nextcloud memory caching

No response

Web server

None

Database

None

Additional info
C: 4 EXAMINE INBOX (QRESYNC (1733797867 441 1:73,81:82,84:97,100:130,159,162,166:168))
S: * FLAGS (\Answered \Flagged \Deleted \Seen \Draft $label1 $junk $notjunk)
S: * OK [PERMANENTFLAGS ()] Read-only mailbox.
S: * 125 EXISTS
S: * 0 RECENT
S: * OK [UNSEEN 92] First unseen.
S: * OK [UIDVALIDITY 1733797867] UIDs valid
S: * OK [UIDNEXT 169] Predicted next UID
S: * OK [HIGHESTMODSEQ 441] Highest
S: 4 OK [READ-ONLY] Examine completed (0.001 + 0.000 secs).
>> Command 4 took 0.058 seconds.
C: 5 SELECT INBOX (QRESYNC (1733797867 441 1:73,81:82,84:97,100:130,159,162,166:168))
S: * OK [CLOSED] Previous mailbox closed.
S: * FLAGS (\Answered \Flagged \Deleted \Seen \Draft $label1 $junk $notjunk)
S: * OK [PERMANENTFLAGS (\Answered \Flagged \Deleted \Seen \Draft $label1 $junk $notjunk \*)] Flags permitted.
S: * 125 EXISTS
S: * 0 RECENT
S: * OK [UNSEEN 92] First unseen.
S: * OK [UIDVALIDITY 1733797867] UIDs valid
S: * OK [UIDNEXT 169] Predicted next UID
S: * OK [HIGHESTMODSEQ 441] Highest
S: 5 OK [READ-WRITE] Select completed (0.001 + 0.000 secs).
>> Command 5 took 0.034 seconds.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing a mailbox sync while watching the IMAP log, then trace the sync path that issues EXAMINE and SELECT. No source file or test is named in the report; done means a sync uses only one of those commands and the duplicate behavior is covered by a regression check.

Written by the indexing model from the issue text.

Assessment

Tech stack
php
Domain
backend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.