# Are Read Receipt Messages ever deleted?

**URL:** <https://forum.delta.chat/t/are-read-receipt-messages-ever-deleted/378>\
**Category:** Uncategorized\
**Created:** [April 20, 2019, 1:36pm UTC](https://forum.delta.chat/t/are-read-receipt-messages-ever-deleted/378 "2019-04-20T13:36:16Z")\
**Posts on this page:** 17\
**Page:** 1

<div class="post-metadata">

**Author:** ![allo](https://forum.delta.chat/user_avatar/forum.delta.chat/allo/32/171_2.png) [@allo](https://forum.delta.chat/u/allo)\
**Post date:** [April 20, 2019, 1:36pm UTC](https://forum.delta.chat/t/are-read-receipt-messages-ever-deleted/378/1 "2019-04-20T13:36:16Z")

</div>

I currently seem to have one read-receipt per message in my Deltachat folder. Can’t they be deleted after the app marked the message as read internally? Or after the next message from the other person arrived (what implies they saw the chat history)? This could free storage space and reduce the number of messages.

---

<div class="post-metadata">

**Author:** ![testbird](https://forum.delta.chat/letter_avatar_proxy/v4/letter/t/ce73a5/32.png) [@testbird](https://forum.delta.chat/u/testbird)\
**Post date:** [April 20, 2019, 1:41pm UTC](https://forum.delta.chat/t/are-read-receipt-messages-ever-deleted/378/2 "2019-04-20T13:41:39Z")

</div>

When and if they can be deleted depends on the multi-device syncing.  
Maybe the first client to see the receipt can adjust the “seen” state of the corresponding sent message, before deleting the receipt. Allowing other clients to pick up the state later on.

---

<div class="post-metadata">

**Author:** ![allo](https://forum.delta.chat/user_avatar/forum.delta.chat/allo/32/171_2.png) [@allo](https://forum.delta.chat/u/allo)\
**Post date:** [April 20, 2019, 1:56pm UTC](https://forum.delta.chat/t/are-read-receipt-messages-ever-deleted/378/3 "2019-04-20T13:56:32Z")

</div>

What about deleting them when I answered the chat? Other clients will be notified that I answered, so the “read” state is synced as well.

---

<div class="post-metadata">

**Author:** ![testbird](https://forum.delta.chat/letter_avatar_proxy/v4/letter/t/ce73a5/32.png) [@testbird](https://forum.delta.chat/u/testbird)\
**Post date:** [April 20, 2019, 2:13pm UTC](https://forum.delta.chat/t/are-read-receipt-messages-ever-deleted/378/4 "2019-04-20T14:13:33Z")

</div>

Seems problematic in group chats where “seen” and “answer” can’t be implied.

---

<div class="post-metadata">

**Author:** ![testbird](https://forum.delta.chat/letter_avatar_proxy/v4/letter/t/ce73a5/32.png) [@testbird](https://forum.delta.chat/u/testbird)\
**Post date:** [April 20, 2019, 2:14pm UTC](https://forum.delta.chat/t/are-read-receipt-messages-ever-deleted/378/5 "2019-04-20T14:14:42Z")

</div>

> <https://github.com/deltachat/deltachat-core/issues/644>
>
> basic multi-device syncing is already available, eg. incoming messages appear on all devices as well as outgoing messages. also new chats...

---

<div class="post-metadata">

**Author:** ![webratte](https://forum.delta.chat/user_avatar/forum.delta.chat/webratte/32/16_2.png) [@webratte](https://forum.delta.chat/u/webratte)\
**Post date:** [April 20, 2019, 5:34pm UTC](https://forum.delta.chat/t/are-read-receipt-messages-ever-deleted/378/6 "2019-04-20T17:34:11Z")

</div>

Fixing this is currently started in

> <https://github.com/deltachat/deltachat-core/pull/595>

---

<div class="post-metadata">

**Author:** ![testbird](https://forum.delta.chat/letter_avatar_proxy/v4/letter/t/ce73a5/32.png) [@testbird](https://forum.delta.chat/u/testbird)\
**Post date:** [April 20, 2019, 5:50pm UTC](https://forum.delta.chat/t/are-read-receipt-messages-ever-deleted/378/7 "2019-04-20T17:50:31Z")

</div>

A history limit won’t get rid of the messy receipts in between the messages on the server or in archived folders.

---

<div class="post-metadata">

**Author:** ![allo](https://forum.delta.chat/user_avatar/forum.delta.chat/allo/32/171_2.png) [@allo](https://forum.delta.chat/u/allo)\
**Post date:** [April 20, 2019, 6:50pm UTC](https://forum.delta.chat/t/are-read-receipt-messages-ever-deleted/378/8 "2019-04-20T18:50:39Z")

</div>

But I think especially for group chats, there are A LOT of read-receipts. And with some text in them, every one of them may even be larger than the message I’ve sent, but after a short time they are not needed anymore.

---

<div class="post-metadata">

**Author:** ![adbenitez](https://forum.delta.chat/user_avatar/forum.delta.chat/adbenitez/32/2323_2.png) [@adbenitez](https://forum.delta.chat/u/adbenitez)\
**Post date:** [April 22, 2019, 2:29pm UTC](https://forum.delta.chat/t/are-read-receipt-messages-ever-deleted/378/9 "2019-04-22T14:29:32Z")

</div>

history limit will solve all the problems for those who don’t want to keep any message in the server, including read receipt 😉

---

<div class="post-metadata">

**Author:** ![webratte](https://forum.delta.chat/user_avatar/forum.delta.chat/webratte/32/16_2.png) [@webratte](https://forum.delta.chat/u/webratte)\
**Post date:** [April 22, 2019, 5:15pm UTC](https://forum.delta.chat/t/are-read-receipt-messages-ever-deleted/378/10 "2019-04-22T17:15:58Z")

</div>

> [@adbenitez](#):
>
> history limit will solve all the problems for those who don’t want to keep any message in the server, including read receipt 😉

And also for all who only would clean up older messages (older then x days) to save storage.

For me it’s no matter, if there younger read receipts or system messages then this x days.

---

<div class="post-metadata">

**Author:** ![adbenitez](https://forum.delta.chat/user_avatar/forum.delta.chat/adbenitez/32/2323_2.png) [@adbenitez](https://forum.delta.chat/u/adbenitez)\
**Post date:** [April 22, 2019, 5:18pm UTC](https://forum.delta.chat/t/are-read-receipt-messages-ever-deleted/378/11 "2019-04-22T17:18:55Z")

</div>

read receipts are not currently of much use in groups, would be good to have an option to disable read receipt in group, it is a lot of waste of emails and we need to long press the message and press the info button to see who read the message, and this for every message 😕

---

<div class="post-metadata">

**Author:** ![webratte](https://forum.delta.chat/user_avatar/forum.delta.chat/webratte/32/16_2.png) [@webratte](https://forum.delta.chat/u/webratte)\
**Post date:** [April 22, 2019, 5:33pm UTC](https://forum.delta.chat/t/are-read-receipt-messages-ever-deleted/378/12 "2019-04-22T17:33:06Z")

</div>

> [@adbenitez](#):
>
> we need to long press the message and press the info button to see who read the message

Ah, great. I didn’t know that. I thought I can’t see that.  
I like this feature 😉

---

<div class="post-metadata">

**Author:** ![adbenitez](https://forum.delta.chat/user_avatar/forum.delta.chat/adbenitez/32/2323_2.png) [@adbenitez](https://forum.delta.chat/u/adbenitez)\
**Post date:** [April 22, 2019, 5:36pm UTC](https://forum.delta.chat/t/are-read-receipt-messages-ever-deleted/378/13 "2019-04-22T17:36:08Z")

</div>

yes but it is a bit too much work to do this every now and them to check if friend X or Y read it or not yet, that is why I was proposing a eye icon with a number of views instead of the double mark for groups, also the current “trick” is a bit hidden, for example you didn’t knew about it

---

<div class="post-metadata">

**Author:** ![webratte](https://forum.delta.chat/user_avatar/forum.delta.chat/webratte/32/16_2.png) [@webratte](https://forum.delta.chat/u/webratte)\
**Post date:** [April 22, 2019, 5:52pm UTC](https://forum.delta.chat/t/are-read-receipt-messages-ever-deleted/378/14 "2019-04-22T17:52:50Z")

</div>

This sounds like a good idea for a later version.

Currently there are much more important thigs to do.

E.G purge older mails from server 😉

---

<div class="post-metadata">

**Author:** ![adbenitez](https://forum.delta.chat/user_avatar/forum.delta.chat/adbenitez/32/2323_2.png) [@adbenitez](https://forum.delta.chat/u/adbenitez)\
**Post date:** [April 22, 2019, 6:06pm UTC](https://forum.delta.chat/t/are-read-receipt-messages-ever-deleted/378/15 "2019-04-22T18:06:38Z")

</div>

for sure,  
server clean up and traffic saving is much more high priority for people with slow/paid networks and limited server 😉

---

<div class="post-metadata">

**Author:** ![allo](https://forum.delta.chat/user_avatar/forum.delta.chat/allo/32/171_2.png) [@allo](https://forum.delta.chat/u/allo)\
**Post date:** [January 27, 2022, 7:50pm UTC](https://forum.delta.chat/t/are-read-receipt-messages-ever-deleted/378/16 "2022-01-27T19:50:04Z")

</div>

> [@adbenitez](#):
>
> history limit will solve all the problems for those who don’t want to keep any message in the server, including read receipt 😉

It would be useful to only delete read receipts, so you can still sync the message history across different clients, but strip the read receipts that are only useful for the short time between sending the message and seeing the checkmark.

---

<div class="post-metadata">

**Author:** ![r10s](https://forum.delta.chat/user_avatar/forum.delta.chat/r10s/32/1513_2.png) [@r10s](https://forum.delta.chat/u/r10s)\
**Post date:** [October 6, 2026, 3:04pm UTC](https://forum.delta.chat/t/are-read-receipt-messages-ever-deleted/378/17 "2026-10-06T15:04:29Z")

</div>


