[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         | Michael Slusarz <slusarz at horde.org>
  Summary            | Incorrectly parses RFC 822 headers that have whitespace
  Queue              | Horde Framework Packages
  Version            | Git master
  Type               | Bug
-State              | Unconfirmed
+State              | Assigned
-Priority           | 3. High
+Priority           | 1. Low
  Milestone          |
  Patch              |
-Owners             |
+Owners             | Michael Slusarz
------------------------------------------------------------------------------


Michael Slusarz <slusarz at horde.org> (2013-04-18 13:21) wrote:

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).