[Tickets #9538] Re: compose/reply malformed header

[bugs at horde.org]

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

Ticket URL: http://bugs.horde.org/ticket/9538
------------------------------------------------------------------------------
  Ticket             | 9538
  Updated By         | Michael Slusarz <slusarz at horde.org>
  Summary            | compose/reply malformed header
  Queue              | IMP
  Version            | Git master
  Type               | Bug
  State              | Feedback
  Priority           | 1. Low
  Milestone          |
  Patch              |
  Owners             | Michael Slusarz
------------------------------------------------------------------------------


Michael Slusarz <slusarz at horde.org> (2011-02-01 16:22) wrote:

> Can you try with courier-imap-4.3.0 and see if you can reproduce the  
> errors ? If not, then I'll try to debug further.

I can reproduce.  The problem is that the parsing of the envelope  
entry is broken.  Instead of finding 10 fields, it only parses 5  
(because the quote is not closed).  This results in various data  
entries not existing even though the API guarantees they should be  
available.

There will never be a way to properly parse this entry - all fields  
after the bad field will be garbage.  But the code should be able to  
handle this more gracefully - by defaulting to blank entries for  
example.  This is going to take a bit of work; my current thinking is  
we should be returning objects from the IMAP library fetch() call and  
deal with the issue of bad data when accessing the object properties.