[delta-dev] Re: Read receipts setting not honored (one-way only)

Hello, I've been experiencing a strange problem with delta for quite a while now: even though I've selected the option to *send* so called "read receipts" I am not receiving them since at least June or so. The strange thing is that instead my client(s) *do* send out receipt upon on read events! 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. 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. How the "receiptiviness" if you allow me term :) is negotiated between clients? Does libdelta send some extra info only upon change setting events? 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. Thanks.