# Responce in group will not be signed with Chat: **URL:** \ **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:** 8\ **Page:** 1
**Author:** ![danfrie](https://forum.delta.chat/letter_avatar_proxy/v4/letter/d/5f8ce5/32.png) [@danfrie](https://forum.delta.chat/u/danfrie)\ **Post date:** [March 13, 2020, 10:05pm UTC](https://forum.delta.chat/t/responce-in-group-will-not-be-signed-with-chat/888/1 "2020-03-13T22:05:16Z")
_Delta Chat version_ Android 1.2.1 _Expected behaviour_ A message in a DeltaChat group should be signed in the Mail-subject with \ to can be moved to the DeltaChat folder and show up in the messenger. _Actual behavior_ A message in a DeltaChat group send with Verion 1.2.1 has just the Mail-subject \ and will not be moved correctly by other members of the group. _Steps to reproduce the problem_ 1. send a message in a DeltaChat group with the DeltaChat messenger version 1.2.1 2. check the mail-subject with a standart mail application ---
**Author:** ![r10s](https://forum.delta.chat/user_avatar/forum.delta.chat/r10s/32/1513_2.png) [@r10s](https://forum.delta.chat/u/r10s)\ **Post date:** [March 14, 2020, 12:05pm UTC](https://forum.delta.chat/t/responce-in-group-will-not-be-signed-with-chat/888/2 "2020-03-14T12:05:06Z")
this is the correct and expected behavior. 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** - see [Subject of emails](https://support.delta.chat/t/subject-of-emails/264/84) ---
**Author:** ![danfrie](https://forum.delta.chat/letter_avatar_proxy/v4/letter/d/5f8ce5/32.png) [@danfrie](https://forum.delta.chat/u/danfrie)\ **Post date:** [March 14, 2020, 12:28pm UTC](https://forum.delta.chat/t/responce-in-group-will-not-be-signed-with-chat/888/3 "2020-03-14T12:28:36Z")
well, thank you for the clearification. Unfortunately it leads to the issue that messages will not be moved to the DeltaChat folder correctly and consequently will not show up in the messanger for some clients. Is there a way to overcome it? ---
**Author:** ![r10s](https://forum.delta.chat/user_avatar/forum.delta.chat/r10s/32/1513_2.png) [@r10s](https://forum.delta.chat/u/r10s)\ **Post date:** [March 14, 2020, 6:08pm UTC](https://forum.delta.chat/t/responce-in-group-will-not-be-signed-with-chat/888/4 "2020-03-14T18:08:37Z")
why does this lead to the issue that messages will not be moved to the DeltaChat folder correctly? the subject is ignored by Delta Chat on receiving messages. ---
**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")
> [@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. ---
**Author:** ![adbenitez](https://forum.delta.chat/user_avatar/forum.delta.chat/adbenitez/32/2323_2.png) [@adbenitez](https://forum.delta.chat/u/adbenitez)\ **Post date:** [March 15, 2020, 5:29am UTC](https://forum.delta.chat/t/responce-in-group-will-not-be-signed-with-chat/888/6 "2020-03-15T05:29:09Z")
hi, do you mean you have a server side rule that used the subject to move messages containing “Chat:” ??? if that is the case, you could try using the “Chat-Version” header instead. (Also Delta Chat itself has an option to move messages to the DeltaChat folder when they are received in the app, it doesn’t matter the subject the chat messages will be moved by the app, if you see some messages left in the INBOX, that is a connection issue and some random messages get stuck in the Inbox since Delta Chat seems not retrying to move them) ---
**Author:** ![danfrie](https://forum.delta.chat/letter_avatar_proxy/v4/letter/d/5f8ce5/32.png) [@danfrie](https://forum.delta.chat/u/danfrie)\ **Post date:** [March 15, 2020, 10:02am UTC](https://forum.delta.chat/t/responce-in-group-will-not-be-signed-with-chat/888/7 "2020-03-15T10:02:01Z")
Hi, thank you all for your replies. I got the problem and all of you are right! Unfortunately it leads to the same issue mentioned here: [Issues with Mail responding](https://support.delta.chat/t/issues-with-mail-responding/887). All messages will be moved and filtered correctly if sended from delta but NOT if replied by a standard email application. In this case a Chat-Tag in the Mail-header is missing, hence a server side rule with Chat-Version (or similar) will not work. Thus what exactly is the tag in the mail header by which delta recognize it as chat-message? And how has this changed in the latest version (with an older version it works perfectly)? (Main issue for this thread is solved) ---
**Author:** ![r10s](https://forum.delta.chat/user_avatar/forum.delta.chat/r10s/32/1513_2.png) [@r10s](https://forum.delta.chat/u/r10s)\ **Post date:** [October 6, 2026, 2:59pm UTC](https://forum.delta.chat/t/responce-in-group-will-not-be-signed-with-chat/888/8 "2026-10-06T14:59:56Z")