Ovo će web mjesto raditi na ograničen način, dok obavljamo održavanje stranice. Ako neki članak ne riješi tvoj problem i ako želiš postaviti pitanje, naša zajednica za podršku spremna je pomoći na Twitteru @FirefoxSupport i na Redditu /r/firefox.

Pretraži podršku

Izbjegni prevare podrške. Nikad te nećemo tražiti da nas nazoveš, da nam pošalješ telefonski broj ili da podijeliš osobne podatke. Prijavi sumnjive radnje pomoću opcije „Prijavi zlouporabu”.

Saznaj više

Edit message as new and references

  • 1 odgovor
  • 1 ima ovaj problem
  • 1 prikaz
  • Posljednji odgovor od Toad-Hall

more options

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.

Svi odgovori (1)

more options

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.