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

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

Learn More

Can't Edit as New Message a previously sent email, replacing message with copied/pasted text in body, to avoid entering all bcc addresses again.

  • 2 ответа
  • 1 имеет эту проблему
  • 7 просмотров
  • Последний ответ от sfhowes

more options

I suddenly cannot send an email with a bcc list that has copied/pasted text in the body of a previously sent email to avoid having to re-enter all the bcc addresses. It just doesn't send. A message flashes for a split second when I hit Send, too fast to read, then nothing. I've always been able to do this before. I'm now using TB Beta.

I suddenly cannot send an email with a bcc list that has copied/pasted text in the body of a previously sent email to avoid having to re-enter all the bcc addresses. It just doesn't send. A message flashes for a split second when I hit Send, too fast to read, then nothing. I've always been able to do this before. I'm now using TB Beta.

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

more options

re : I'm now using TB Beta. What version of beta?

I did locate this info: https://www-stage.thunderbird.net/en-US/thunderbird/88.0beta/releasenotes/ Thunderbird 88.0beta is using a new implementation of the message sending code that is easier to maintain and more flexible. As with any major change, bugs are bound to happen. The old behavior can be restored by setting the preferences "mailnews.send.jsmodule" and "mailnews.smtp.jsmodule" to false.


It may be helpful if you could report this issue in bugzilla. You would need to register to post bugs. They would need to know what OS you use and what version of Thunderbird beta. Plus all the info about the method you are using and the result you get. https://bugzilla.mozilla.org/home

Изменено Toad-Hall

more options

Does the message have attachments? You may be seeing this bug, fixed in 89b3.