Zoeken in Support

Vermijd ondersteuningsscams. We zullen u nooit vragen een telefoonnummer te bellen, er een sms naar te sturen of persoonlijke gegevens te delen. Meld verdachte activiteit met de optie ‘Misbruik melden’.

Meer info

Deze conversatie is gearchiveerd. Stel een nieuwe vraag als u hulp nodig hebt.

problem with command line arguments

  • 1 antwoord
  • 1 heeft dit probleem
  • 48 weergaven
  • Laatste antwoord van 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.

Gekozen oplossing

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

Dit antwoord in context lezen 👍 1

Alle antwoorden (1)

more options

Gekozen oplossing

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