Welcome to Delta Chat! A read receipt should be sent if both chat partners have enabled it in the settings. However, not to confuse the user with hundreds of read receipts, Delta Chat automatically marks them as seen and moves them to the "DeltaChat" folder in your mailbox, so have a look there. Read messages then get two checkmarks, just as you know it from other messengers. Does this explain the confusion? On 02.12.20 00:35, Marco Vittorini Orgeas wrote:

How have you determined it? The read receipts you send out are not saved in your mailboxes. Other users get double tick for the messages you sent in 1:1 chat? This bug is not gone, rather closed as WONTFIX. DC uses non-standard Chat-Disposition-Notification-To rather than standard Disposition-Notification-To header for reasons mentioned there. DC should sent Chat-Disposition-Notification-To header in outgoing messages. Check that it is true. The logic is simple: Chat-Disposition-Notification-To header is sent out in every normal (not read receipt itself) message if read receipt setting is enabled. If a message with Chat-Disposition-Notification-To header is received, it is marked as a message "read receipt requested". When you read it, your client will send out a read receipt if the setting for read receipts is enabled. Make sure not to use lower version than the one you exported backup from, as there is no version check on importing, downgrade is allowed. But this should not be the cause in your case.

On Wed, 2 Dec 2020 17:03:21 +0300 Alexander Krotov <ilabdsf(a)gmail.com> wrote: That and in addition I see an extra SMTP send transaction in the MTA log after I read a message. The bug report was opened after this discussion https://support.delta.chat/t/delta-chat-not-sending-read-receipts-any-more/… which originally described a problem very similar to the one I'm experiencing. Then somebody else stepped in and kind of derailed the discussion by opening an issue to take in consideration standard MUAs. I'll file another report if the need arises. As already said, I confirm that this happens *only* for outbound messages towards regular MUA contacts. I don't see any "Chat-Disposition-Notification-To" header inside outbound *and* inbound messages between myself and DeltaChat confirmed contacts despite the relative setting being turned on. If that's the case, i.e.: libdelta just uses a custom disposition header, and reacts to it, then I could be hitting a bug. Strangest thing is my delta clients still send receipts even in absence of it. The import was done into on a much bigger version of the android client. Afterwards I also added the desktop version to the mix by importing the backup. As I experience the problem with both I wonder if my DB is somehow corrupted. Anything else I could check in this direction for further investigation? -- Marco CONFIDENTALITY NOTICE: The information contained in this message as well as the attached file(s) is confidential/privileged and is only intended for the person to whom it is addressed. If the reader of this message is not the intended recipient or the employee or agent responsible for delivering the message to the intended recipient, or you have received this communication in error, please be aware that any dissemination, distribution or duplication is strictly prohibited, and can be illegal. Please notify us immediately and delete all copies from your mailbox and other archives. Thank you ------------------------------------------------------------------------ In ottemperanza con il nuovo Regolamento Europeo GDPR n. 679/2016, le informazioni contenute in questo messaggio sono riservate e confidenziali. Il loro utilizzo è consentito esclusivamente al destinatario del messaggio, per le finalità indicate nel messaggio stesso. Qualora Lei non fosse la persona a cui il presente messaggio è destinato, La invitiamo ad eliminarlo dal Suo Sistema ed a distruggere le varie copie o stampe, dandocene gentilmente comunicazione. Ogni utilizzo improprio è contrario ai principi del nuovo Regolamento Europeo GDPR n. 679/2016.