288950 - wrong mail address in message composer's "To" field due to misfitting Mozilla -compose command line syntax

Status: RESOLVED EXPIRED

(Core Graveyard :: Cmd-line Features, defect)

Description

[kko]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; de-AT; rv:1.7.6) Gecko/20050319
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; de-AT; rv:1.7.6) Gecko/20050319

When you follow the Steps to Reproduce, in both cases the command line
'mozilla.exe -compose "to=mailto:[e-mail]"' is generated and executed by
the Windows OS. But Mozilla expects the command line to be 
'mozilla.exe -compose "to=[e-mail]"'.

The message compose syntax should be 'mozilla.exe -compose
"to=mailto:[e-mail]"' instead of 'mozilla.exe -compose
"to=[e-mail]"'. The algorithm, that extracts the target 
mail address out of the command line, has to be changed accordingly.

See also comments on bugs 
https://bugzilla.mozilla.org/show_bug.cgi?id=236774
and
https://bugzilla.mozilla.org/show_bug.cgi?id=58810

Reproducible: Always

Steps to Reproduce:
1) Mozilla Mail is set up as your default mail client (associated with mailto
protocol). Create a new text file and paste the following:

[InternetShortcut]
URL=mailto:[e-mail]

Rename the file from "<somename>.txt" to "<somename>.url" and double click it.

OR

2) Mozilla Mail is set up as your default mail client (associated with mailto
protocol) and preference "network.protocol-handler.external.mailto" is set to
"true".

Open a HTML page containing <a href="mailto:[e-mail]">mail</a> in Mozilla
Browser and click on that link.
Actual Results:  
In both cases, Mozilla Mail's message compose window will open. Now look at the
"To" field. It's value is "mailto:[e-mail]" instead of "[e-mail]"
and you have to manually correct it every time! (If you don't, the message will
be sent, but of course can't be delivered)

Expected Results:  
The "To" field should contain "[e-mail]".

Comment 1

[Gervase Markham [:gerv]]

This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/

Comment 2

[Gervase Markham [:gerv]]

This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.