nextcloud / nextcloud/mail

Mail archived on third-party client not archived (and is unreadable) in Mail

Open
#10,662 2 comments 0 reactions 1 assignee View on GitHub

@SebastianKrupinski is already working on this.

Since Apr 23, 2025.

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

Description

Steps to reproduce

I would have followed up on the previous issue (#8223) while it was still open, but i didn't want to be a constant nag.

  1. Open Nextcloud mail and click refresh button to bring Nextcloud Mail up to date:
    Image
    Image

  2. Open third party email client and archive message:
    Image

  3. Wait a few seconds to ensure the archived message is properly archived in imap server
    Image
    Image

  4. Go back to Nextcloud Mail and click refresh button again to ensure nextcloud has synced with the imap server:
    Image

  5. See email still in Nextcloud Mail inbox:
    Image

  6. Try opening email on Nextcloud Mail:
    Image

Since I haven't seen other reports about this still being an issue, perhaps it's just my configuration/setup/imap server?

Expected behavior

I would expect the email to also be archived on Nextcloud after I archive the email in FairEmail.

Actual behavior

The email is not archived on Nextcloud mail, and the email is not readable.

Mail app version

4.2.0-rc.3

Nextcloud version

30.0.4

Mailserver or service

Purelymail FairEmail Version 1.2262a (Fdroid)

Operating system

Ubuntu 22.04

PHP engine version

PHP 8.2

Nextcloud memory caching

memcache.local

Web server

Apache (supported)

Database

MariaDB

Additional info

I should clarify, that clicking the "Repair" button in the Nextcloud Mail inbox does properly move the email to archive, but this isn't ideal since I'm constantly clicking the "Repair" button.

I'm using the Nextcloud VM

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.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.