# Responce in group will not be signed with Chat:

**URL:** <https://forum.delta.chat/t/responce-in-group-will-not-be-signed-with-chat/888>\
**Category:** Mutual Help\
**Created:** [March 13, 2020, 10:05pm UTC](https://forum.delta.chat/t/responce-in-group-will-not-be-signed-with-chat/888 "2020-03-13T22:05:16Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![testbird](https://forum.delta.chat/letter_avatar_proxy/v4/letter/t/ce73a5/32.png) [@testbird](https://forum.delta.chat/u/testbird)\
**Post date:** [March 14, 2020, 6:17pm UTC](https://forum.delta.chat/t/responce-in-group-will-not-be-signed-with-chat/888/5 "2020-03-14T18:17:00Z")

</div>

> [@r10s](#):
>
> the goal is, to be as much compatible to existing mailing programs as possible - so there is a simple rule now: **the group name is the subject**

As existing mailing programs can receive multiple different subjects, I think sooner or later **group** chats will need to support receiving emails with changed subjects without prompting (emails from known contacts).

What if emails would be assigned to chats by their `From:` and `To:` fields, but not the subject?

It could mean incoming emails result in group name changes, or not. For mailing list support it seems the group name could preferably stay the same, using what is often mentioned within brackets `[Listname] Subject...`

And later maybe [a “subject” filtering tab](https://support.delta.chat/t/subject-of-emails/264/77) in the options available by tapping the chat’s title bar.

---

_[View the full topic](https://forum.delta.chat/t/responce-in-group-will-not-be-signed-with-chat/888)._