misc/135420: gnats generates broken In-Reply-To headers

>Number:         135420
>Category:       misc
>Synopsis:       gnats generates broken In-Reply-To headers
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-bugs
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Tue Jun 09 16:50:01 UTC 2009
>Closed-Date:
>Last-Modified:
>Originator:     David Wolfskill
>Release:        7.2-STABLE
>Organization:
Wolfskill & Dowling Residence
>Environment:
FreeBSD albert.catwhisker.org 7.2-STABLE FreeBSD 7.2-STABLE #115 r193375: Wed Jun  3 05:52:41 PDT 2009     [e-mail]:/common/S3/obj/usr/src/sys/ALBERT  i386

>Description:
Here's an excerpt (yeah, but/pasted) from the headers of a recent gnats acknowledgement of a submitted PR:

| From: [e-mail]
| Subject: Re: docs/133855: New mailing list, freebsd-gecko
| Reply-To: [e-mail], [e-mail]
| In-Reply-To: Your message of Sun, 19 Apr 2009 07:10:26 -0700 (PDT)
|         <[e-mail]>
| Status: RO
| Content-Length: 434
| Lines: 14

Note the content of the In-Reply-To header: that is syntactically incorrect, as RFC 2822, section 3.6.4 contains:

| 3.6.4. Identification fields
| 
|    Though optional, every message SHOULD have a "Message-ID:" field.
|    Furthermore, reply messages SHOULD have "In-Reply-To:" and
|    "References:" fields as appropriate, as described below.
| 
|    The "Message-ID:" field contains a single unique message identifier.
|    The "References:" and "In-Reply-To:" field each contain one or more
|    unique message identifiers, optionally separated by CFWS.
| 
|    The message identifier (msg-id) is similar in syntax to an angle-addr
|    construct without the internal CFWS.
| 
| message-id      =       "Message-ID:" msg-id CRLF
| 
| in-reply-to     =       "In-Reply-To:" 1*msg-id CRLF
| 
| references      =       "References:" 1*msg-id CRLF
| 
| msg-id          =       [CFWS] "<" id-left "@" id-right ">" [CFWS]
| ...

Note that there is no defined syntax for commentary in the In-Reply-To header.

[I cannot claim credit for noticing this first.  A correspondent informed me of it, in my capacity as [e-mail].]

>How-To-Repeat:
File a PR at FreeBSd.org, then examine the headers of the acknowledgement email message.
>Fix:


>Release-Note:
>Audit-Trail:
>Unformatted:
_______________________________________________
[e-mail] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "[e-mail]"