2 Dec
2020
2 Dec
'20
2:03 p.m.
The strange thing is that instead my client(s) *do*
send out receipt
upon on read events!
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?
Initially I've attributed the thing to
https://github.com/deltachat/deltachat-core-rust/issues/1610 but seen
that the bug seems long gone, I suspect something else is going on.
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.
To dig a little deeper I need some extra info:
I've looked at some
messages and it seems libdelta sends out an extra
"Disposition-Notification" header only to *non* delta chat clients.
DC should sent Chat-Disposition-Notification-To header in outgoing
messages. Check that it is true.
How the "receiptiviness" if you allow me
term :) is negotiated between
clients? Does libdelta send some extra info only upon change setting
events?
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.
I should probably add that I've also experienced a
really bad upgrade
back in August because F-Droid did bump the version to a major one
after months and the process did not went well, no messages were
received and I had to resort by making a backup, and importing the
thing after an installation from the Play Store.
Do libdelta checks data integrity/correct format before importing? I
don't think this is the cause but am wondering if the backup was
"somehow" corrupt.
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.