Windows 10 reached EOS (end of support) on October 14, 2025. For more information, see this article.

Buscar en Ayuda

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

problem with command line arguments

  • 1 respuesta
  • 1 tiene este problema
  • 39 visitas
  • Última respuesta de Toad-Hall

more options

Since updating Thunderbird from 60.8 to 68.0 (both 32-bit) my batch script, which is supposed to open a new email form and fill in some data, doesnt seem to work anymore. Here is the script:

"C:\Program Files (x86)\Mozilla Thunderbird\thunderbird.exe" -compose "to=Test@Example.de,from=Test2@Example.de,subject=Example,body=ExampleBody,attachment=file:///C:/Test.txt"

If I run this script an empty new email form appears. In 60.8 this form would be filled with the information from the batch script. This script works if I exclude the attachment attribute, but I need to attach it automatically.

Has anything changed regarding command line arguments or am I doing something wrong here? Thank you in advance.

Since updating Thunderbird from 60.8 to 68.0 (both 32-bit) my batch script, which is supposed to open a new email form and fill in some data, doesnt seem to work anymore. Here is the script: "C:\Program Files (x86)\Mozilla Thunderbird\thunderbird.exe" -compose "to=Test@Example.de,from=Test2@Example.de,subject=Example,body=ExampleBody,attachment=file:///C:/Test.txt" If I run this script an empty new email form appears. In 60.8 this form would be filled with the information from the batch script. This script works if I exclude the attachment attribute, but I need to attach it automatically. Has anything changed regarding command line arguments or am I doing something wrong here? Thank you in advance.

Solución elegida

I believe this is a known bug and should be fixed for 68.1.0 https://bugzilla.mozilla.org/show_bug.cgi?id=1577117

Leer esta respuesta en su contexto 👍 1

Todas las respuestas (1)

more options

Solución elegida

I believe this is a known bug and should be fixed for 68.1.0 https://bugzilla.mozilla.org/show_bug.cgi?id=1577117