<<< Date Index >>>     <<< Thread Index >>>

Re: [Mutt] #1611: mutt erroneously omits information in parenthesis



#1611: mutt erroneously omits information in parenthesis after addresses in Cc
headers
-----------------------------------------+----------------------------------
  Reporter:  Marco d'Itri <md@xxxxxxxx>  |       Owner:  mutt-dev
      Type:  defect                      |      Status:  new     
  Priority:  minor                       |   Milestone:          
 Component:  mutt                        |     Version:  1.5.20  
Resolution:                              |    Keywords:          
-----------------------------------------+----------------------------------

Comment(by vinc17):

 Replying to [comment:7 Derek Martin]:
 > It is likewise explicitly allowed in RFCs 2822, and 822, and 733.
 >
 > Note that 822 and 733 are standards; the more recent ones are not (not
 > that it matters in this case).

 No, RFC 2822 is a ''proposed standard'' therefore '''is a standard'''.
 From RFC 4677:
 {{{
 There are six kinds of RFCs:

    o  Proposed standards

    o  Draft standards

    o  Internet standards (sometimes called "full standards")

    o  Informational documents

    o  Experimental protocols

    o  Historic documents

    Only the first three (proposed, draft, and full) are standards within
    the IETF.
 }}}

-- 
Ticket URL: <http://dev.mutt.org/trac/ticket/1611#comment:8>
Mutt <http://www.mutt.org/>
The Mutt mail user agent