Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

non-group-messages from non-Delta-Client to multiple recipients do not create ad-hoc group #1349

Closed
r10s opened this issue Mar 20, 2020 · 2 comments · Fixed by #1357
Closed
Assignees
Labels
bug Something is not working

Comments

@r10s
Copy link
Member

r10s commented Mar 20, 2020

i received a mail form a non-Delta-Client today, sent to three recipients - afaik, these kind or mails should create an ad-hoc group with the recipients (or maybe resue an existing group), however, the mail show up in the normal one-to-one-chat.

this is bad, as replies are not sent to all reicpient, also, it is invisible to the Delta user who are the recipients.

similar forum entry: https://support.delta.chat/t/deltachat-doesnt-group-messages-as-before-regression/829

@r10s r10s added the bug label Mar 20, 2020
@r10s
Copy link
Member Author

r10s commented Mar 22, 2020

tested this with a fresh delta-account, show-classic-mails=all - everything works as expected, so, not sure if my description above is really correct, i am failing to to reproduce it.

@r10s
Copy link
Member Author

r10s commented Mar 22, 2020

k, i found an issue:

  • setup new delta chat for Alice-Delta, show-classic-mail=accepted
  • send message from Alice to Bob-NonDelta (this creates Bob as a contact)
  • send a ad-hoc-group-messages from Bob-NonDelta to Alice-Delta and Claire

=> the ad-hoc-group-message will not create an ad-hoc-group for Alice

@r10s r10s self-assigned this Mar 23, 2020
@r10s r10s added the bug Something is not working label Aug 12, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something is not working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant