Open
Bug 678521
Opened 14 years ago
Updated 2 years ago
Accept URI-encoded arguments on commandline
Categories
(Thunderbird :: OS Integration, enhancement)
Thunderbird
OS Integration
Tracking
(Not tracked)
NEW
People
(Reporter: u422140, Unassigned)
References
Details
Thunderbird should accept URI-encoded strings as arguments for the -compose commandline command. The motivation is to be able to include certain characters that are normally used to quote strings or separate the arguments.
Example: let's consider the following commandline string:
> thunderbird -compose "to='John, Doe <nobody@example.cz>,',cc='Copy machine <nobody@example.cz>,',bcc='Big Brother <nobody@example.cz>,',subject=Hello%20world%21,body=Hi%2C%20this%20is%20the%20body.,attachment='/tmp/Nabídkový_rozpočet_vše.pdf,/tmp/Další Nabídkový_rozpočet_vše.pdf'"
By running this, the recipient's address would get split in two. Same thing would happen when an attachment filename contains a comma. I tried to play with quoting, moving apostrophes or specifying multiple "attachment=" arguments but didn't have luck.
Also please notice that the Subject and Body fields get unescaped by Thunderbird just fine. Suggest to do the same for all arguments. This report may sound like RFE but the inconsistency is an issue.
We're calling the compose command from xdg-email script, a cross-desktop command for sending e-mails. It is used by many applications and thus affecting overall desktop functionality in larger scale.
FYI, https://developer.mozilla.org/en/Command_Line_Options doesn't cover the scenario I've described
Updated•12 years ago
|
Component: General → Untriaged
Status: UNCONFIRMED → NEW
Type: defect → enhancement
Component: Untriaged → OS Integration
Ever confirmed: true
OS: Linux → All
Hardware: x86_64 → All
See Also: → 1577117
Version: 5.0 → Trunk
This is still reproducible on Windows 10 with V68.3. Escaping all command line arguments is probably an overdue feature. As bug 1577117 demonstrates these command lines are still in use.
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•