Important Notice: We're experiencing email notification issues. If you've posted a question in the community forums recently, please check your profile manually for responses while we're working to fix this.

On Monday the 3rd of March, around 5pm UTC (9am PT) users may experience a brief period of downtime while one of our underlying services is under maintenance.

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

Path to attachment temp file incomplete

  • 1 réponse
  • 1 a ce problème
  • 125 vues
  • Dernière réponse par sfhowes

more options

Hi everyone,

on a Windows 10 machine, an error occurred when trying to open mail attachments. The path to the temporary file that is passed to the appropriate application arrives incomplete. If the filename contains a dot or whitespace, it will be cut at that position: E.g. "path\file.1.pdf" or "path\file 1.pdf" is received as "path\file." or "path\file ".

I can confirm that the attachment files exists and can be opened manually from the expected location, e.g. "%appdata%\local\temp\".

This must have happened during the last 2 weeks. Before that, everything worked as expected. Windows 10 and Thunderbird are up to date.

Do you have a hint what might have caused this and how to fix it?

Hi everyone, on a Windows 10 machine, an error occurred when trying to open mail attachments. The path to the temporary file that is passed to the appropriate application arrives incomplete. If the filename contains a dot or whitespace, it will be cut at that position: E.g. "path\file.1.pdf" or "path\file 1.pdf" is received as "path\file." or "path\file ". I can confirm that the attachment files exists and can be opened manually from the expected location, e.g. "%appdata%\local\temp\". This must have happened during the last 2 weeks. Before that, everything worked as expected. Windows 10 and Thunderbird are up to date. Do you have a hint what might have caused this and how to fix it?

Toutes les réponses (1)

more options

Solution choisie