[Tickets #12189] Re: Incorrectly parses RFC 822 headers that have whitespace

[noreply at bugs.horde.org]

DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: http://bugs.horde.org/ticket/12189
------------------------------------------------------------------------------
  Ticket             | 12189
  Updated By         | stuart.carnie at gmail.com
  Summary            | Incorrectly parses RFC 822 headers that have whitespace
  Queue              | Horde Framework Packages
  Version            | Git master
  Type               | Bug
  State              | Assigned
  Priority           | 1. Low
  Milestone          |
  Patch              |
  Owners             | Michael Slusarz
------------------------------------------------------------------------------


stuart.carnie at gmail.com (2013-04-18 19:59) wrote:

Yes, I totally agree.  And yes you are correct, RFC 5322 (which itself  
obsoletes 2822) is the current; my apologies.  In section 2.1 General  
Description, it still refers to the separation as an empty line:

    A message consists of header fields (collectively called "the header
    section of the message") followed, optionally, by a body.  The header
    section is a sequence of lines of characters with special syntax as
    defined in this specification.  The body is simply a sequence of
    characters that follows the header section and is separated from the
    header section by an empty line (i.e., a line with nothing preceding
    the CRLF).

Cheers,

Stu

> FWIW, RFC 822 is long since obsolete.  RFC 5322 is the controlling standard.
>
> I'll need to look into RFC 5322 to see if this is allowable.  At a  
> minimum, this is an example of a sub-standard MUA sending these kind  
> of messages (it makes 0 sense to have trailing whitespace in an  
> unstructured header).