Windows 10 reached EOS (end of support) on October 14, 2025. If you are on Windows 10, see this article.

Avatar for Username

Поиск в поддержке

Избегайте мошенников, выдающих себя за службу поддержки. Мы никогда не попросим вас позвонить, отправить текстовое сообщение или поделиться личной информацией. Сообщайте о подозрительной активности, используя функцию «Пожаловаться».

Подробнее
Эта тема была архивирована. Если вам нужна помощь, задайте новый вопрос.
Архивировано

Edit message as new and references

Thunderbird Другое
Toad-Hall отвечено
pawlikwn
pawlikwn

I have question/proposal about "Edit as New message". When I am using this option I expect that everything in my message is new except Body and Emails (Sender/Receivers etc.). Therefore in Thunderbird whole message's header remains unchanged. It makes, that in 'new message' email references stay, so when someone is grouping messages by threads, that 'new message' is part of old thread. In my opinion it is closer to "Reply as New message" feature than "Edit..."

So, maybe that is thing that Mozilla team should think about: Remove references to other emails from header when using "Edit as New message" or create new option that will really make new message.

Greetings, Pawel.

I have question/proposal about "Edit as New message". When I am using this option I expect that everything in my message is new except Body and Emails (Sender/Receivers etc.). Therefore in Thunderbird whole message's header remains unchanged. It makes, that in 'new message' email references stay, so when someone is grouping messages by threads, that 'new message' is part of old thread. In my opinion it is closer to "Reply as New message" feature than "Edit..." So, maybe that is thing that Mozilla team should think about: Remove references to other emails from header when using "Edit as New message" or create new option that will really make new message. Greetings, Pawel.

Все ответы (1)

Toad-Hall
Toad-Hall
  • Топ-25 помощников

This has already been posted as a bug and I believe the developers are looking into this. https://bugzilla.mozilla.org/show_bug.cgi?id=1254666

It looks as if this fix will be released soon as bug has been marked as 'resolved/fixed'. This does not mean it is resolved in the version you are using but it is a note for developers that they have dealt with it for up and coming version.