Ticket #1484901 (closed Bugs: fixed)

Opened 7 months ago

Last modified 6 months ago

Automated emails from livejournal.com don't display dates

Reported by: minneyar Owned by:
Priority: 5 Milestone: 0.2-alpha
Component: PHP backend Version: 0.1-stable
Severity: minor Keywords:
Cc:

Description

As the summary says, e-mails sent from livejournal.com do not display anything in the "date" column, although they are sorted correctly. When viewing the message, the "Date:" field is also empty. When I view the raw headers, the date is obviously present. Here are the headers from an example message:

Return-Path: <lj_notify@livejournal.com>
X-Original-To: x@x.com
Delivered-To: x@x.com
Received: by x.com (Postfix, from userid 1013)
	id 265497B9E; Fri, 14 Mar 2008 19:54:42 -0500 (CDT)
X-Spam-Checker-Version: SpamAssassin 3.2.3 (2007-08-08) on
	x.x.com
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 required=5.0 tests=AWL,BAYES_00,
	RCVD_IN_DNSWL_LOW,SPF_HELO_PASS autolearn=ham version=3.2.3
Received: from livejournal.com (livejournal.com [204.9.177.18])
	by x.com (Postfix) with ESMTP id 617577B9D
	for <x@x.com>; Fri, 14 Mar 2008 19:54:34 -0500 (CDT)
Received: from localhost (theschwartz [127.0.0.1])
	by livejournal.com (TheSchwartzMTA) with ESMTP id 64c32a9b3792c1f10450fbd1835325740061068287;
	Sat, 15 Mar 2008 00:54:34 +0000 (UTC)
Content-Transfer-Encoding: binary
Content-Type: multipart/alternative; boundary="_----------=_120554247371831"
MIME-Version: 1.0
X-Mailer: MIME::Lite 3.01 (F2.72; A1.62; B3.04; Q3.03)
Date: Sat, 15 Mar 2008 00:54:33 UT
From: "x - LJ Comment" <lj_notify@livejournal.com>
To: x@x.com
Subject: Reply to your comment...
Message-Id: <x@livejournal.com>
In-Reply-To: <x@livejournal.com>
References: <x@livejournal.com> <x@livejournal.com>
X-Lj-Journal: x

I've also attached a screenshot showing what the main message list looks like.

Attachments

roundcubeerror1.png (180.2 kB) - added by minneyar 7 months ago.

Change History

Changed 7 months ago by minneyar

  Changed 7 months ago by alec

"Sat, 15 Mar 2008 00:54:33 UT" is not a correct date/time string. It should be formatted according to rfc2822.

  Changed 6 months ago by thomasb

  • component changed from Interface to PHP backend
  • severity changed from normal to minor

Maybe we could consider a fallback stripping off the timezone part if parsing fails.

follow-up: ↓ 4   Changed 6 months ago by minneyar

Out of curiosity, what part of that string isn't correct? I've gone through the specification at http://www.faqs.org/rfcs/rfc2822.html, and it seems valid to me, but maybe I'm missing something.

in reply to: ↑ 3   Changed 6 months ago by alec

Replying to minneyar:

Out of curiosity, what part of that string isn't correct?

UT

  Changed 6 months ago by alec

  • status changed from new to closed
  • resolution set to fixed
  • milestone changed from later to 0.1.2

Fixed in r1324

Note: See TracTickets for help on using tickets.