nextcloud / nextcloud/mail

Disable storing sent message on IMAP when SMTP server does this automatically

Open
#4,831 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

Expected behavior

Have only 1 copy of sent messages

Actual behavior

There is 2 copies of sent messages

This is not exactly problem of the Mail app.
This exact problem is presented on a lot of mail clients (thunderbird, mailspring)
On thunderbird can be solved by Disabling to keep a copy of sent message to Sent folder.

I think what is happening is.
You send a message, mailApp puts a copy on Sent folder
Outlook server ALSO places a copy on Sent folder after forwarding the message
Local copy synced to server and Server copy synced to Local
and you end up with 2 sent copies.

So, an option like this will probably fix it.

  • Keep a copy of sent message to sent folder
Mail app

Mail app version: 1.9.4

Mailserver or service: Outlook

Server configuration

Operating system: Unraid

Web server: Nginx

Database: PostgreSQL

PHP version: 7.4.15

Nextcloud Version: 20.0.8

Client configuration

Browser: Chrome 89

Operating system: Windows10

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

No source files, tests, or entry points are named. Start by locating the sent-message handling and settings entry points, then verify the Outlook scenario described in the issue. Done means users can disable keeping a local sent-message copy so only the server-created copy remains.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript, php
Domain
backend
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.