88441 - mailto: URI should respect other mail headers specified, according to RFC 2368

Status: RESOLVED DUPLICATE of bug 260482

(MailNews Core :: Composition, defect)

Description

[Matthew Mastracci]

User-Agent: Mozilla/4.0 (compatible; MSIE 5.01; Windows NT 5.0)
BuildID:    2001062904

The above URI should compose a message containing an In-Reply-To header.

Comment 1

[Christopher Hoess (gone)]

Confirming.  See also bug 11459 for comments on a fuller implementation of
mailto:  URLs; we may not wish mailto: to access the full range of mail headers,
but RFC 2368 apparently suggests the nature of such restrictions, as per bug 74308.

Comment 2

[Jesse Ruderman]

-> message composition

Comment 3

[timeless]

.

Comment 4

[James Collier]

This one doesn't seem to have had any attention for a long time.

Mailing list archive sites commonly supply In-Reply-To: and References: headers
in mailto URIs. This allows users to respect threading when responding to a post.

RFC 2368 rightly cautions against blind implementation of mailto headers, but
gives In-Reply-To: as an example of its use.  My vote would go to implementing
these two - I can't see any real danger (can anyone else??), and I believe they  

   * would be useful

   * would conform to RFC 2368 and

   * would be in keeping with current expected practice.

If I had any reservation it would be because the user has no way of viewing
these headers when composing a message - but that limitation applies equally
when replying to a mail or newsgroup message. 

Comment 5

[Mike Cowperthwaite]

The specific request for this bug -- an In-Reply-To header -- has a patch that 
should be checked in shortly at bug 260482.  Looking at that patch, it's clear 
that the current code requires specific support for each header, rather than 
providing a general handler for  <mailto:[e-mail]?X-Header:foo>  as implied 
by the summary of this bug.  Dupe, or not?

(Yes, that bug is filed under TB, but the code in the patch is shared backend.)

Comment 6

[J Luh]

Marking as duplicate of 260482 per comment 5 since, as noted in comment 1,
mailto: should not support all headers, and 260482 covers In-Reply-To.

*** This bug has been marked as a duplicate of 260482 ***