l

Unify event emitter types for context and account manager

4

This is a proposal on top of #3421, breaking C API to unify event emitter types for contexts and account manager.

Event loop stopping is not thread-safe

8

Common usage of deltachat-ffi API, as described in the doxygen documentation, is to start an OS thread with event loop, pass a `dc_context_t` pointer to it and let it process...

Messages without From field are not trashed

3

Here UNKNOWN contact should probably be treated as blocked: https://github.com/deltachat/deltachat-core-rust/blob/7bcb03f1eca2114f8a387b03f60abdf31c7e988b/src/dc_receive_imf.rs#L392

Remove direct dependency on futures-lite

1

#skip-changelog

Add API to change database passphrase

5

New API is: - dc_context_is_encrypted() - dc_context_change_passphrase()

Add expiration_timestamp column to imap table

4

I propose to add a column `expiration_timestamp` to `imap` table which will say when the message should be deleted from IMAP server. This column should be calculated at the time...

Currently `markseen_msgs` creates `MarkseenMsgOnImap` job only if the chat is unblocked: https://github.com/deltachat/deltachat-core-rust/blob/cccdc51ad40f7c28447b00aff685f108a29976aa/src/message.rs#L1333 Because of this, if you read the contact request chat on one device, the messages are not marked...

Encrypted messages with attachments don't have protected-headers="v1" in the header

1

This line does not work for `multipart/mixed` parts: https://github.com/deltachat/deltachat-core-rust/blob/36aef6499d0c2e2787cc8ee2bd798a6c9a7400a0/src/mimefactory.rs#L591 The result is still `Content-Type: multipart/mixed; boundary="some-random-string"`, so Thunderbird does not look for protected headers and displays message Subject as `...`.

Remove the last non-standard footer, not the first one

7

If there are multiple non-standard footers, like ``` Message -------------- more info -------------- footer ``` DC currently cuts the message after the first `--------------` rather than the last.