Tickets :: [#6053] Obsolete but valid RFC 2822 headers not accepted

Summary	Obsolete but valid RFC 2822 headers not accepted
Queue	Horde Groupware Webmail Edition
Queue Version	1.0
Type	Bug
State	Not A Bug
Priority	1. Low
Owners
Requester	alex (at) softgrow (dot) com
Created	12/27/2007 (6471 days ago)
Due	01/29/2008 (6438 days ago)
Updated	12/28/2007 (6470 days ago)
Assigned
Resolved	12/28/2007 (6470 days ago)
Github Issue Link
Github Pull Request
Milestone
Patch	No

12/28/2007 08:58:40 AM	Jan Schneider	Comment #2 State ⇒ Not A Bug	Reply to this comment
Horde does not parse any time strings. This is either the c-client library or PHP's strtotime() implementation on your system.

12/27/2007 10:21:25 PM	alex (at) softgrow (dot) com	Comment #1 State ⇒ Unconfirmed Priority ⇒ 1. Low Type ⇒ Bug Summary ⇒ Obsolete but valid RFC 2822 headers not accepted Due ⇒ 01/29/2008 Queue ⇒ Horde Groupware Webmail Edition	Reply to this comment
RFC 2822 requires mail clients to accept Obosolete time zone specifications in the "Date" field of the message. http://www.faqs.org/rfcs/rfc2822.html (section 4.1 and Section 4.3) If a date field in a message is "Date: 26 DEC 07 17:06:27 UT" it displays as "Unknown Date" in the message list view. UT should be interpreted as +0000