IMP 6.1.8.

Changes have been made in Git (master):

commit 36bab91996bbcca36e32ed0b397d46ecece605d4
Author: Michael M Slusarz <slusarz@horde.org>
Date:   Mon Apr 14 16:33:52 2014 -0600

     [mms] Better handling of malformed message dates in mailbox 
listing (Bug #13114).

     Conflicts:
             imp/docs/CHANGES
             imp/package.xml

  imp/docs/CHANGES       |    2 ++
  imp/lib/Mailbox/Ui.php |    4 ++++
  imp/package.xml        |    1 +
  3 files changed, 7 insertions(+), 0 deletions(-)

http://github.com/horde/horde/commit/36bab91996bbcca36e32ed0b397d46ecece605d4

Changes have been made in Git (FRAMEWORK_5_1):

commit aa5f5488aba268606b555a40d22e4258e214fd6d
Author: Michael M Slusarz <slusarz@horde.org>
Date:   Mon Apr 14 16:33:52 2014 -0600

     [mms] Better handling of malformed message dates in mailbox 
listing (Bug #13114).

  imp/docs/CHANGES       |    2 ++
  imp/lib/Mailbox/Ui.php |    4 ++++
  imp/package.xml        |    2 ++
  3 files changed, 8 insertions(+), 0 deletions(-)

http://github.com/horde/horde/commit/aa5f5488aba268606b555a40d22e4258e214fd6d

Thank  you for your quick reply.  Below is the trace for the entire 
communication.  I placed a single message in an empty folder.  I 
apologize that the trace is not the standard IMP trace format but I 
think the output is clear enough.

If you suspect that this is not a bug, please go ahead and close this 
ticket as it is not worth spending much time on since the message is 
so poorly formatted to begin with.

Thanks in advance.  Aria


-----> C= 1397512543 testuser CLIENT: sd [8]
2 SELECT test


-----> C= 1397512543 testuser SERVER: sd [13]
* 1 EXISTS
* 1 RECENT
* OK [UNSEEN 1] Message 1 is first unseen
* OK [UIDVALIDITY 619998768]
* OK [UIDNEXT 2] Predicted next UID
* FLAGS (\Seen \Answered \Flagged \Deleted \Draft)
* OK [PERMANENTFLAGS (\Seen \Answered \Flagged \Deleted \Draft)]
2 OK [READ-WRITE] SELECT completed


-----> C= 1397512543 testuser CLIENT: sd [8]
3 UID SEARCH ALL


-----> C= 1397512543 testuser SERVER: sd [13]
* SEARCH 1


-----> C= 1397512543 testuser SERVER: sd [13]
3 OK UID SEARCH completed


-----> C= 1397512543 testuser CLIENT: sd [8]
4 UID SEARCH UNSEEN


-----> C= 1397512543 testuser SERVER: sd [13]
* SEARCH 1


-----> C= 1397512543 testuser SERVER: sd [13]
4 OK UID SEARCH completed


-----> C= 1397512543 testuser CLIENT: sd [8]
5 UID FETCH 1 (INTERNALDATE ENVELOPE)


-----> C= 1397512543 testuser SERVER: sd [13]
* 1 FETCH (INTERNALDATE "13-Apr-2014 21:04:47 -0400" ENVELOPE (NIL {15}
Alert Message!! ((NIL NIL "EDGE-CORE-SWITCH" "your.domain")) ((NIL NIL 
"EDGE-CORE-SWITCH" "your.domain")) ((NIL NIL "EDGE-CORE-SWITCH" 
"your.domain")) ((NIL NIL "sys-support" "your.domain")) NIL NIL NIL 
NIL) UID 1)


-----> C= 1397512543 testuser SERVER: sd [13]
5 OK UID FETCH completed


-----> C= 1397512543 testuser CLIENT: sd [8]
6 UID FETCH 1 (FLAGS RFC822.SIZE BODY.PEEK[HEADER.FIELDS (IMPORTANCE 
LIST-POST X-PRIORITY CONTENT-TYPE)])


-----> C= 1397512543 testuser SERVER: sd [13]
* 1 FETCH (FLAGS (\Recent) RFC822.SIZE 435 BODY[HEADER.FIELDS 
(IMPORTANCE LIST-POST X-PRIORITY CONTENT-TYPE)] NIL UID 1)


-----> C= 1397512543 testuser SERVER: sd [13]
6 OK UID FETCH completed


-----> C= 1397512543 testuser CLIENT: sd [8]
7 EXAMINE INBOX


-----> C= 1397512543 testuser SERVER: sd [13]
* 237 EXISTS
* 0 RECENT
* OK [UIDVALIDITY 453665752]
* OK [UIDNEXT 227161] Predicted next UID
* FLAGS (\Seen \Answered \Flagged \Deleted \Draft)
* OK [PERMANENTFLAGS ()]
7 OK [READ-ONLY] EXAMINE completed


-----> C= 1397512543 testuser CLIENT: sd [8]
8 LOGOUT


-----> C= 1397512549 testuser PROXY: user tracing disabled. Expect 
further output until client logou                                       
     t.

Cannot reproduce.

I'm guessing your IMAP server is possibly to blame in not being able 
to parse that (admittedly) malformed date.  With Dovecot 2.2.11 I see 
this

C: 5 UID FETCH 61713 (ENVELOPE FLAGS RFC822.SIZE 
BODY.PEEK[HEADER.FIELDS (IMPORTANCE LIST-POST X-PRIORITY CONTENT-TYPE)])
S: * 18 FETCH (UID 61713 FLAGS (\Recent) RFC822.SIZE 414 ENVELOPE 
("Apr 13 20:4:48" "Alert Message!!" ((NIL NIL "EDGE-CORE-SWITCH" 
"your.domain")) ((NIL NIL "EDGE-CORE-SWITCH" "your.domain")) ((NIL NIL 
"EDGE-CORE-SWITCH" "your.domain")) ((NIL NIL "someone" "your.domain")) 
NIL NIL NIL NIL) BODY[HEADER.FIELDS (IMPORTANCE LIST-POST X-PRIORITY 
CONTENT-TYPE)] {2}
S: [LITERAL DATA: 2 bytes]
S: )
S: 5 OK Fetch completed.

It passes Apr 13 20:4:48 directly back, which is parsed by PHP into 
4/13 @ 20:04:48 of the current year (verified via unit test).

An IMAP log of the ENVELOPE return on your system would be useful for 
further debugging.


To further debug this issue, we need details of the IMP -> IMAP/POP 
communication.

To enable debugging, see instructions contained in 
imp/config/backends.php (the 'debug' config parameter).

Debugging should not be enabled on a production server,   Attach/post 
only the portion of the log that directly deals with the problem 
reported (it may be simplest to clear the log file and then perform 
the event that causes the error).

Changes have been made in Git (master):

commit 4dabffbdfe2cbaab9b49a71f90ee03942386cd7c
Author: Michael M Slusarz <slusarz@horde.org>
Date:   Mon Apr 14 12:39:55 2014 -0600

     Add test for Bug #13114

  .../test/Horde/Imap/Client/DateTimeTest.php        |   39 
++++++++------------
  1 files changed, 16 insertions(+), 23 deletions(-)

http://github.com/horde/horde/commit/4dabffbdfe2cbaab9b49a71f90ee03942386cd7c

Hi,
Not sure if this is a bug or working as designed but I wanted to 
report that when a message is received with no proper date header in 
the message, then the displayed date in the date column on the IMP 
message window is the time you logged into IMP.  That is, each time 
you login to IMP, the poorly composed message will show the login time 
in the 'Date' column in the display.  Below is an example of a raw 
message (happens to be from a hardware switch).  Other clients like 
Outlook display the actual arrival time.

Thanks.

Received: from EDGE-CORE-SWITCH [123.456.789.0] by mail.your.domain   
via TCP with SMTP ; Sun, 13 Apr 2014 21:04:47 EDT
From: <EDGE-CORE-SWITCH@your.domain>
To: someone@your.domain
Subject: Alert Message!!

Date: Apr 13 20:4:48
Message: There is a log.
Level: 6
Module: SNMP
Function: 1
Error: 1
Time: Apr 13 20:4:36
Host: EDGE-CORE-SWITCH
Content: STP port state: MSTID 0, Eth 1/29 becomes forwarding.