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

problem with command line arguments

  • 1 resposta
  • 1 tem este problema
  • 41 visualizações
  • Última resposta por 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 "[email protected],[email protected],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 "[email protected],[email protected],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.

Solução escolhida

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

Ler esta resposta no contexto 👍 1

Todas as respostas (1)

more options

Solução escolhida

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