Probe existing email contacts upon installation for easy onboarding

[ian]

• A user would install DC
• On first start, DC would scan for email addresses (along with fingerprints and public keys) in the device address book, the IMAP folder of the DC accounts of the user and possible further “external” IMAP accounts (not otherwise added to DC). If any entry has an email address not known to DC, DC would send a probe email to it.
• If DC on the other side accepts this contact and proceeds with encrypted communication, extend the device address book entry with the public key and connect it to the contact profile within DC (a separate feature request?)
• Otherwise mark this contact as ignored
• Such a scan may be repeated periodically

The following issue asked for something similar, but it was marked as solved without fixing the main request:

Propose contacts in the first installation

I think it would be very comfortable, more social and intuitive, if in the first installation. Delta would scan the sent folder and automatically add some email addresses to the delta contacts, (at least the most recent ones) in this way the new users would already have something to do

[ian]

Further contact list integration, sync, import and export related issues:

OS contacts integration

Expected behavior It would be great if delta chat would integrate with native addressbook on the system because: It could pick profile pictures that are already there. It could recognize messages from the same people even when they respond with different emails. Actual behavior At the moment it does not appear that native address book is used at all. So every correspondent appears as circle with initials. Even better if public keys could be stored in corresponding address books so other apps…

How to make Deltachat use phone contact?

Currently it display all email addresses I used to send and receive. How to make it use only my phone contact? Delta Chat version 1.14.5 Expected behavior Deltachat should access and use contact from phone. Actual behavior Deltachat currently compiles contact from all email addresses that I use to send and receive from my account. Steps to reproduce the problem Setup and use Deltachat normally Screen snapshots

Using/importing contacts on desktop program

Hi, I think it would be very nice to use the CardDAV address book of your mail provider in Delta Chat. In the current state you have to type in the mail address and name, if you want to chat with someone. Those information are already in my CardDAV address book What do you think?

Android: Open Contacts Integration

Some people use a separate address-book app on android to keep their real contact list away from apps like facebook or whatsapp. One of this app is OpenContacts(F-Droid|sourcecode). This would require a bit of collaboration with OpenContacts on a feature to expose api for getting access to the contacts: https://gitlab.com/sultanahamer/OpenContacts/-/issues/77 I believe having an address book where you can specify what app is allowed to access which fields on the contact is usefull. You could e…

Contacts management

Delta Chat imports correctly the contacts but it’s impossible to export or manage them. Expected behavior Edit the contacts, export vCard Actual behavior Contacts can’t be edited (the address, contact name only is possible) and can’t be exported as vCard

Easy identification of Delta Chat contacts and phone contacts

Users can’t not differentiate easily between DC contacts and phone contacts, perhaps showing a little badge with a delta sign or another visual clue for the users would help them identify the contact type. I propose something like this: [Screenshot_20190116-123450] Expected behavior Users can easily know which contact are created on DC only and which are phone contacts. Actual behavior All contacts look the same, users can’t know if a given contact is in DC database or in the phone database…

Kontakte Android

Hallo, ich bin ein Neuling hier. Mir gefällt Delta.Chat App ausgezeichnet. Meine Frage bezieht sich auf die Android-Version. Auf meinem Smartphone habe ich Kontakte hinterlegt, die nur im Gerätespeicher (vcf-Format) sind und bewusst nicht mit Google syncronisiert werden sollen. Gibt es eine Möglichkeit (oder ist sie geplant) das Deltachat die Adressen aus einem “Ordner meiner Wahl” bezieht? Wäre ein coole Sicherheitsoption

Contact names from address book

I would like to have the option to choose the source for displayed contact names. Currently, only nicknames given in the DC client are used, with a fallback to the name provided with the mail by the sender. However, the highest priority for me (and I assume many others) would be to use the name saved in my device’s address book. I would propose to add a tier in between, resulting in the following order to determine the displayed name: Nickname given in the DC client (no change) Name associate…

Contacts management

Delta Chat imports correctly the contacts but it’s impossible to export or manage them. Expected behavior Edit the contacts, export vCard Actual behavior Contacts can’t be edited (the address, contact name only is possible) and can’t be exported as vCard

Favourite contacts

Make possible to favourite contacts will allow users to easily identify they real contacts from contacts automatically added from a group, or that users don’t use to talk to. Favourite contacts will be shown at the top of the list in the contacts list. Initially all contacts in the phone’s contacts will be marked as favourite.

Better contact handling

It’s a bit difficult (if not extremely tedious), when we change accounts in DC, export our contacts Expected behavior We are able to send more than one contact info at the same time (if not all), with the possibility to export it as vCard (or any other format) too. Actual behavior afaik current method (as of DC v1.0.0) is to send a message to the recipient with contact name and a clickable email

Add contact as vCard

If I tab the attache button “contact” it would be nice if I could choose a contact from system contact App (address book) as vCard. Currently is only a mailaddress.

[link2xt]

We had this feature for scanning fro the IMAP folder before, but it was just removed:

feat: do not collect email addresses from messages after configuration

There are practically no public keys sent unencrypted in the latest versions of DC, so you will not be able to collect anything other than email addresses this way.

@ian

If any entry has an email address not known to DC, DC would send a probe email to it.

This will just spam all non-DC users with probe emails asking to send back the key. We also normally don’t reply back automatically to anything. During SecureJoin we reply, but only if a known “invite code” from the scanned QR code is sent.

[ian]

Note that the account of the existing phone and IMAP contacts may support one or more of:

• WKD
• Autocrypt
• HKPS

Autocrypt headers and public key attachments could also be scraped from the IMAP inbox without requiring to send a new ping mail.

A DC user may also have the choice to submit their key to HKPS hosts.

Given how often such requests are raised on the forum (many linked), are you sure dismissing it immediately is the best course of action?

[ian]

At the same time, the feature of notifying your email contacts who you could not upgrade about you joining DC and telling them how to encrypt your connection could also be useful to some. Many messaging apps and social networking services supported such a feature in the past. The key here is to skip those who you have already contacted about this or have already added. DC should also pop up a list of checkboxes for each proposed person, so the user could confirm echa before sending a ping.

[irvan-putra]

I think most of the proposals have outdated assumption about how DeltaChat works, i also just realized it with the closing of WKD topic, that DeltaChat won’t publish the public keys:

The life-changing magic of WKD

anyways, this seems to be diverging a lot from the initial topic, so let’s resume the answer to the initial question and close it, if something different needs to be discussed or problems reported, better create new on-point threads: it is unlikely we ever support WKD, we don’t want people to discover public keys, that is in direct contradiction with the anti-spam protection of open-registration email servers (a.k.a chatmail)

So with that, we won’t realize if that contact actually use DeltaChat.

I think at this point, if DeltaChat still support sending email to classic-email (see FAQ - Delta Chat ), we can just auto generate an invite link to chatmail in the footer of the email, so the other party will realize that they can continue the conversation at DeltaChat.

So with that, side-stepping the possible spamming if we just automate the probing.

[ian]

Note that the WKD topic contained too many off topic messages, and the closing reason mentioned that chatmail is not planned to support WKD right now.

However, the other aspect was not addressed there: adding support for looking up WKD of a new contact (i.e., when the other peer is not on chatmail/DC)!