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

Rechercher dans l’assistance

Évitez les escroqueries à l’assistance. Nous ne vous demanderons jamais d’appeler ou d’envoyer un SMS à un numéro de téléphone ou de partager des informations personnelles. Veuillez signaler toute activité suspecte en utilisant l’option « Signaler un abus ».

En savoir plus
Ouvert

Forwarding issue with folders using a space for end user

kgumbs

End user reported he is unable to forward emails. Through troubleshooting found the issue only in folders he named first name last initial for example "John S" were unable to forward emails and forward button did not work, but folders name with just first name "John" forward without issue. He changed John S type folders to John folder and forwarding worked in the renamed folder. No adds-on exist for this user as they are blocked for our end users. I had him check Error logs and got the following error message:

Uncaught (in promise) NS_ERROR_OUT_OF_MEMORY: Component returned failure code: 0x8007000e (NS_ERROR_OUT_OF_MEMORY) [nsIMsgComposeService.OpenComposeWindow]

   ComposeMessage chrome://messenger/content/mailCommands.js:443
   _composeMsgByType chrome://messenger/content/mailCommon.js:898

3 mailCommands.js:443:34

End user reported he is unable to forward emails. Through troubleshooting found the issue only in folders he named first name last initial for example "John S" were unable to forward emails and forward button did not work, but folders name with just first name "John" forward without issue. He changed John S type folders to John folder and forwarding worked in the renamed folder. No adds-on exist for this user as they are blocked for our end users. I had him check Error logs and got the following error message: Uncaught (in promise) NS_ERROR_OUT_OF_MEMORY: Component returned failure code: 0x8007000e (NS_ERROR_OUT_OF_MEMORY) [nsIMsgComposeService.OpenComposeWindow] ComposeMessage chrome://messenger/content/mailCommands.js:443 _composeMsgByType chrome://messenger/content/mailCommon.js:898 3 mailCommands.js:443:34

Toutes les réponses (4)

- What version of Thunderbird?

- What is the operating system?

- Please describe in detail what, exactly, happens when they try to forward a message. Please quote all error messages they see.

- Try restarting Thunderbird in Troubleshoot Mode (see <Help | Troubleshoot Mode>). Does the behavior change?

- Perhaps the folder indexes are corrupt. To repair them, right-click on the folder name, choose Properties, then Repair Folder. Follow up by compacting the folder (right-click on the folder name, choose "Compact Folder".)

I just tested this with folders I made with those exact names. Thunderbird versions 153.7esr, 159, and 160 all running on Windows 10 or 11. All messages forward as expected. So, there's some other factor at play than just the folder names.

The End user in question: OS - Windows 11 25h2 Thunderbird Version - 159.0

As stated in my description when clicking the forward button in any folder he has with a space between the first name and last name initial the button does not work. However, when going to folder with just a first name the forward button works and opens a new message window/tab for him to then forward the email. No error messages appear when he attempts to forward from those folders named with that naming scheme.

We tried a repair before I proceed with having him change the folder name to remove last name initial but it did nothing. I had him use the error console by using Ctrl+Shift+J keys and only showed the errors window with the output I posted in my original post:

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Uncaught (in promise) NS_ERROR_OUT_OF_MEMORY: Component returned failure code: 0x8007000e (NS_ERROR_OUT_OF_MEMORY) [nsIMsgComposeService.OpenComposeWindow]

  ComposeMessage chrome://messenger/content/mailCommands.js:443
  _composeMsgByType chrome://messenger/content/mailCommon.js:898

3 mailCommands.js:443:34 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

When we tried troubleshooting mode he stated after the restart it did not fix the issue. He had to rename the folder to get the forward button to work.

I can't reproduce this, but there apparently somebody else could, and if I read the bug report correctly, it's slated to be fixed in release version 161.

https://bugzilla.mozilla.org/show_bug.cgi?id=2088260

There seems to be other factors in play, some:

- The folder with the space in the name is a SUBfolder;

- It may need to be a POP3 account;

- The user might use either EWS (Microsoft 365/Exchange Online) or Proton Mail Bridge.

I don't have the time and ability to test all combinations of these. The subfolder thing doesn't make any different for me. But as I said, it should be fixed in the next release.

This is the exact issue he reported, thank you for confirming this is a bug.

It is occurring on subfolders with a space which I described:

  • - The folder with the space in the name is a SUBfolder;

We will wait till version 161.0 becomes available to confirm no further issues.

Poser une question

Vous devez vous identifier avec votre compte pour répondre aux messages. Veuillez poser une nouvelle question, si vous n’avez pas encore de compte.