28 Mar
2019
28 Mar
'19
1:09 p.m.
Hi Victor,
i'd like to focus in this thread on the API issues
with non-chat "normal" mails ...
On Thu, Mar 28, 2019 at 13:19 +0100, Viktor Pracht wrote:
When considering sending/receiving non-chat mime-messages:
- sending: how does Delta Chat persist the message?
currently a message always relates to a chat id,
i.e. there is precisely one chat for each message.
How would UIs access non-chat messages
when they want to display it later? Or would the messages
be stored outside of DCC's DB and DCC would only
perform Autocrypt processing before sending it out?
- receiving: with which chat is an incoming
message associated? How is it persisted
and then accessed/noted by a UI?
Which events are emitted?
- there also are questions on how Autocrypt
plays into the sending/receiving side
but i *guess* there are doable so i leave
that aside for the moment.
if these questions still do not make sense i am happy
to do an a/v about this topic sometime :)
holger
How does
Autocrypt-handling happen including encryption and decryption? If mime-mails are not tied
to a chat at sending time, but to a caller-specified list of recipients, then how are they
accessed on the receiving side?
I'm not sure I understand the question. Mails are accessed using a mail client, aka
MUA (mail user agent). Why should anything be different if the sender's MUA is using
DCC instead of e.g. MailCore 2?