Open Bug 351863 Opened 14 years ago Updated 10 years ago

thunderbird -remote mailto doesn't allow multiple addresses


(Thunderbird :: General, defect)

Not set


(Not tracked)


(Reporter: rnelson, Unassigned)


User-Agent:       Mozilla/5.0 (X11; U; Linux i686 (x86_64); en-US; rv: Gecko/20060728 SUSE/ Firefox/
Build Identifier: Thunderbird Version 1.505 (20060725)

Mozilla allows commands like:

mozilla -remote "mailto(,"
mozilla -remote "mailto(John Q. Public<>)"


thunderbird -remote "mailto(,"

only sends to the first addressee, and

thunderbird -remote "mailto(John Q. Public<>)"

reports a parse error.

Reproducible: Always

Steps to Reproduce:
1. Start an instance of thuinderbird under linux
2. Give the commands listed above

Actual Results:  
for multiple urls specified, only the first is used for a To field
for full user names specified, a parse error occurs
I can confirm thunderbird -remote "mailto(," only uses the first address. SeaMonkey current trunk works ok. 

thunderbird -remote "mailto(John Q. Public<>)" works fine for me 

Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9a1) Gecko/20060909 Thunderbird/3.0a1 ID:2006090903, branch too
Ever confirmed: true
Summary: thunderbird -remote mailto doesn't allow multiple addresses or full person names → thunderbird -remote mailto doesn't allow multiple addresses
Well, I found a way to make these things work.

1. Multiple recipients in the -remote "mailto" argument.
Contrary to the documentation, a comma separated list doesn't work.  The following does:

thunderbird -remote 'mailto(<>?cc=<>&cc=<>&'

Note how weird this is - we need a question mark as a separator between the first two addresses and an ampersand between subsequent pairs.  I have no idea why this is required.

2. Specifying user names in the "mailto" list.
It seems that "mailto" argument parsing chokes on spaces.  If you just replace them with "%20", everything is fine - here's an example:

thunderbird -remote 'mailto(John%20Doe<>)'

At the very least, these things need to be documented somewhere accessible.  I can't find any up to date documentation on the -remote options anywhere.

Keywords: mail1
Version: unspecified → 1.5
Assignee: mscott → nobody
no activity for a long time, should be closed
That's not a valid reason to close a bug.
You need to log in before you can comment on or make changes to this bug.