Este site irá ter funcionalidade limitada enquanto fazemos manutenção para melhorar a sua experiência. Se um artigo não resolve o seu problema e quiser colocar uma questão, temos a nossa comunidade de apoio à espera de o ajudar em @FirefoxSupport no Twitter, /r/firefox no Reddit.

Pesquisar no apoio

Evite burlas no apoio. Nunca iremos solicitar que telefone ou envie uma mensagem de texto para um número de telefone ou que partilhe informações pessoais. Por favor, reporte atividades suspeitas utilizando a opção "Reportar abuso".

Saber mais

Some email trails are being trimmed by some third-party email software

  • 6 respostas
  • 1 tem este problema
  • 7 visualizações
  • Última resposta por Tom

more options

This question is maybe related to my previous question about thunderbird 78 email trails not being handled nicely by external email software: https://support.mozilla.org/en-US/questions/1307465

This is the offending scenario:

  • Someone sends me a email (Text-A)
  • I reply (Text-B with Text-A quoted)
  • I get a reply (Text-C with Text-B quoted and ideally Text-C quoted at level 2)

The problem is that in the third email, the quoted Text-C is now missing in some cases after the "On DATE, PERSON wrote:"

This question is maybe related to my previous question about thunderbird 78 email trails not being handled nicely by external email software: https://support.mozilla.org/en-US/questions/1307465 This is the offending scenario: * Someone sends me a email (Text-A) * I reply (Text-B with Text-A quoted) * I get a reply (Text-C with Text-B quoted and ideally Text-C quoted at level 2) The problem is that in the third email, the quoted Text-C is now missing in some cases after the "On DATE, PERSON wrote:"

Solução escolhida

I confirm that what I am facing it this TB 78 bug: https://bugzilla.mozilla.org/show_bug.cgi?id=1675507

The improper characters I was referring to in (https://support.mozilla.org/en-US/questions/1307465) is actualy the same TB 78 bug. See commetns 23 and 25 in that bug report: https://bugzilla.mozilla.org/show_bug.cgi?id=1675507#c23 https://bugzilla.mozilla.org/show_bug.cgi?id=1675507#c25

The good news is that their is a simple fix: setting `mail.html_sanitize.drop_conditional_css` to `false` solves the problem.

Ler esta resposta no contexto 👍 0

Todas as respostas (6)

more options

Quoted text is a decision folks make when they reply to you. If you got an email reply from me for instance it will almost always be trimmed unless I am replying inline. I abhore the duplication that occurs when I have the whole thread in a threaded view and then get the entire thread send back to me with a one or two line comment. I have no interest at all in the quoted text and it contributes nothing to my understanding.

more options

Thanks Matt. I have confirmed with the persons I was emailing with that this was not trimmed on purpose by them. It happened several times as well.

more options

Also, I see my different but probably related question (https://support.mozilla.org/en-US/questions/1307465) was wrongly closed as duplicate but I couldn't find a way to reopen it.

more options
more options

If this is always from replies to you, then I'd suspect their software is doing the trimming. (even if they aren't intentionally)

As a test, build your own message/reply thread to and from yourself (ideally using two different e-mail addresses) and see if by using only TB (and even the same installation on the same machine with the same profile) produces the same result. If not, then TB (your installation anyway) is not the culprit.

more options

Solução escolhida

I confirm that what I am facing it this TB 78 bug: https://bugzilla.mozilla.org/show_bug.cgi?id=1675507

The improper characters I was referring to in (https://support.mozilla.org/en-US/questions/1307465) is actualy the same TB 78 bug. See commetns 23 and 25 in that bug report: https://bugzilla.mozilla.org/show_bug.cgi?id=1675507#c23 https://bugzilla.mozilla.org/show_bug.cgi?id=1675507#c25

The good news is that their is a simple fix: setting `mail.html_sanitize.drop_conditional_css` to `false` solves the problem.