@tchambers The forum at https://support.delta.chat/

Thanks for your patience, everything should work again.

@ulveon As for the RCPT TO: addresses, they are needed for delivery, but they are not stored on the sending server once the message is delivered and the receiving server only sees recipients from the same server. Chatmail relay users also normally have randomly generated addresses, not the […]

@ulveon IMAP does not require any headers, you can even deliver a message without headers into inbox. The only header that is checked by chatmail relays is the From: header, it should have a corresponding DKIM signature to prevent address spoofing. SMTP has a MAIL command with FROM: parameter […]

@xoagray @ulveon
We have an FAQ entry: https://delta.chat/en/help#message-metadata
Delta Chat protects headers (Subject, display name in the From: field, To field etc.) with https://www.rfc-editor.org/rfc/rfc9788.html
You don't need to trust the server for metadata protection. Chatmail relays […]

@castaway see "security" section in wikipedias article https://en.wikipedia.org/wiki/Telegram_(software)

@fuat2mb @delta_chat it's a neat idea to postpone server choice until later, and onboard with some default.

#deltachat apps are currently learning to use multiple addresses at once ("multi-transport"), along with cryptographic hardening against evil server operators. The goal is to provide […]

two other things that can't be stressed enough for maintaining development long-term:

- Avoid superflous abstractions. Premature abstractions are the root of all ... complexity. If you have a second and third case, you can introduce an abstraction, but even then: don't over-abstract!

- write […]

two other things that can't be stressed enough for maintaining development long-term:

- Avoid superflous abstractions. Premature abstractions are the root of all ... complexity. If you have a second and third case, you can introduce an abstraction, but even then: don't over-abstract!

- write […]