I’d like when I set “ALL” for “Show classic emails” I receive all the emails, even by non-contacts, without accepting a contact request.
Or at least I need a notification for the requests.
Otherwise the risk is to read important emails after days.
This should probably be a separate setting “automatically accept contact requests” which you can enable if you don’t worry about spam.
8 Likes
disabling contact requests should also be the default for bots (bot config key should also enable it)
currently bots have to add extra code to handle the first messages of new contacts correctly.
4 Likes
This is something very expected, some clients have been waiting for an answer that I could not give immediately.
1 Like
+1 please
2 Likes
Is there any chance this feature could be implemented or any expected timeframe for it? Maybe we could make a crowdfund to support making this one as a priority? I would go for it!! What about others?
1 Like
I do not think it is necessary to add configuration for this, if the user selects “All” in the configuration of interaction with mail, then allow the entry of all the emails without so much obstacles
I must clarify something, despite having a particular interest in this function, my main interest is based on the usability of DeltaChat, unlike many of you I manually install Delta to many people and I can see this feature as a brake for many users non-technological, in fact, I have found users who find out with me when I check their mobile, of requests that have more than one month, and I have to remind them to check this frequently.
1 Like
Yes, I want to use DeltaChat in our organization instead of Spike and it would surely ease its adoption to novice users. Also, I use DC on 3 devices and it bothers me to allow the same contact three times…
If I will get under spam attack, I can change the behaviour back or use spam filter of mail server…
1 Like
“Contact request” UI seems to have been designed this way in the late 2019/early 2020 and has not changed much since then.
Typical problem on Android is when you receive a notification for contact request and click “Mark read” to dismiss the notification. You may later vaguely remember that you have seen this message somewhere, but can’t recall which chat it was. On the chatlist screen it is nowhere to find, because it went into “contact requests”. There is no such problem on Desktop because it doesn’t have “Mark read” option in the notification, at least for me.
If you remember to check “Contact requests” menu item later, it is not easy to click through all the messages there. You open the “contact requests” chat, click on one message, make a decision and get back to the chatlist screen automatically. To process another request, you need to click “contact requests” item in the menu again.
There were some discussions about redoing “Contact requests” on IRC with @Hocuri and @r10s when dc_msg_get_real_chat_id() was introduced. @Simon also wanted to introduce a badge with a number of unread contact requests so you can check how many contact requests are there without having to enter the “Contact requests” chat, this will require to add support for DC_CHAT_ID_DEADDROP (internal name for “Contact requests”) to ChatId::get_msg_cnt.
Long term, there is an idea to get rid of “contact requests” chat and replace it with a “contact requests” chatlist similar to “archived chats”. The “Contact requests” item should then stay at the top of your chatlist as long as there is at least one unread message in any of the “contact requests” chats.
Edit: there was also a related discussion on GitHub: tweak contact requests · Issue #1896 · deltachat/deltachat-android · GitHub
2 Likes
Something that occurs to me without any user interface change, allow a previously confirmed contact to open directly in the chat, currently if there is no open chat with that contact, the message goes to contact request, the correct thing in my humble opinion is that if there has already been a previous iteration with that contact, do not send the contact request and open the chat directly.
This would improve things a lot
After some peer-to-peer and IRC discussions, the plan is to get rid of the “contact requests” chat and menu item completely, and simply drop contact requests as chats in the chatlist, but with a “[New]” badge, similar to how archived chats are marked with “[Archived]”.
Such chats will not generate notifications and generally act as muted chats. When opened, you can read messages in them, but no read receipts will be sent. The message composition area at the bottom of the screen will be replaced with buttons “Block” and “Accept”, so you can’t send messages until you make a decision. No “Later” option, you can simply go back if you don’t want to decide yet.
2 Likes
thanks for summing up, @link2xt. i’d like to add that this approach also solves other issues we have with contact requests.
- it is hard to keep track of contact-requests as all messages appear in the same chat
- one has to perform contact requests one after the other, this is mitigated by #1898, however it is not solved.
- no ambiguity on tapping on contact-request messages - “show full message”, enlarge-images etc. work as usual.
finally, less things to explain - we can strike the “contact requests” main menu item 
Honestly I don’t understand why new chats should not generate notifications, I think it is important that when you are contacted for the first time on DC you are notified of the event so you can immediately decide what to do (accept or block the contact and possibly decide whether to mute the chat), otherwise you may not notice the start of a new chat even for long periods and this goes against the idea of having DC as if it were an IM for email.
1 Like
This is what @r10s proposed in IRC:
but i think, contact request should still not be notified (maybe we can have an option at some point)
I don’t have any opinion on this, for me it’s not that important whether I get contact requests notifications or not. The chat will appear near the top anyway, unless user has a whole screen of pinned chats. This is a tradeoff between potentially missing a new chat or getting annoyed by spam if your spam filter is not so good.
I’ll probably go with whatever is easier to implement first, maybe send notification for new chat once but treat the chat as muted afterwards, and then we can decide on whether an option is needed based on feedback.
4 Likes
This, in my opinion, could be a good solution
Same for me. It is important to not miss new message/even if it is from unknown person.
2 Likes
Exactly. I expect Delta Chat to mimic a chat/messenger app as much as it can, e.g. Facebook Messenger, Twitter DM. Unless I explicitly blacklisted/blocked someone or I explicitly disabled messaging from strangers, I expect to receive his/her messages!
2 Likes
“Contact requests” chat is going to be removed in the next major release:
3 Likes