[Tickets #13114] Re: Odd received date behavior with poorly composed mail message

[noreply at bugs.horde.org]

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

Ticket URL: http://bugs.horde.org/ticket/13114
------------------------------------------------------------------------------
  Ticket             | 13114
  Updated By         | Michael Slusarz <slusarz at horde.org>
  Summary            | Odd received date behavior with poorly composed mail
                     | message
  Queue              | IMP
  Version            | 6.1.7
  Type               | Bug
-State              | Unconfirmed
+State              | Feedback
  Priority           | 1. Low
  Milestone          |
  Patch              |
-Owners             |
+Owners             | Michael Slusarz
------------------------------------------------------------------------------


Michael Slusarz <slusarz at horde.org> (2014-04-14 12:43) wrote:

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