l

Looks like it is closed by #5669

All the jobs have been removed, now they are explicitly called from inbox loop: #3457

I made a new PR which simply moves fetch directly after IDLE: https://github.com/deltachat/deltachat-core-rust/pull/4974 Unlike old PR, new PR moves fetch call rather than doing fetch twice per iteration.

There is a corresponding desktop issue: https://github.com/deltachat/deltachat-desktop/issues/2722 New deltachat-rpc-client bindings are now uploaded to PyPI #4523. New JSON-RPC bindings are no longer experimental, e.g. [email protected] and matterbridge are using it,...

There is an attempt to fix at #4555, but it does not consider the discussion at #3817, the issue closed in favor of this one. As a first step I...

This will also allow us to get rid of the `sanitize-filename` dependency.

The problem starts with a mimeparser, which stores `is_mime_modified` for the whole message rather than a part: https://github.com/deltachat/deltachat-core-rust/blob/4767f1ce743d2170142c3cc126838d55505eb807/src/mimeparser.rs#L103 Whether to display "Show Full Message..." should be decided per part, not...

Some thoughts about the API design and keeping backward compatibility. Events emitted by the context go into the event channel and, if enabled, to the debug logging XDC. I have...

> Is the process crashing really an issue? Relying on events across restarts seems sketchy The bot may be restarted right before processing an event that is still in the...

@adbenitez > about persistent event processing, I am not sure about them unless the state is consistent, or the events contain enough info, ex. how useful it is to a...