Re: Cannot parse IMAP command after update

[David Maus <dmaus@ictsoc.de>]

At Sat, 17 May 2014 23:12:04 -0700,
Erik Hetzner wrote:
> 
> At Sat, 17 May 2014 14:42:24 -0700,
> Nick Lanham wrote:
> > 
> > Sure, this seems to be the relevant bit (i.e. everything that happens in the log after I hit 'A' in a summary buffer to try and reply quoted):
> > 
> > *elmo-imap437* OK arrived
> > [14:39:58] => ((ok nil))
> > [14:39:58] -> mailbox size adjusted: [Gmail]/Drafts, (0 . 0)
> > [14:39:58] -> elmo-imap438 BAD Could not parse command
> > *elmo-imap438* BAD arrived
> > [14:39:58] =>((bad (nil "Could not parse command")))
> 
> Hi Nick,
> 
> Thanks for this. Unfortunately in this case the command was not logged
> in the debug log (it seems that the function elmo-imap4-send-command
> does not always log before sending a command to the server), but I
> could see that the problem was with creating drafts in gmail and was
> able to reproduce the problem. I added a line to debug the command and
> this the source of the error:
> 
>   [22:47:17] <- elmo-imap413 append [Gmail]/Drafts ()  "17-May-2014 22:47:17 -0700" {512}
>   [22:47:17] -> elmo-imap413 BAD Could not parse command
> 
> I am not that familiar with IMAP but I will look into this. In the
> meantime, perhaps somebody else more familiar with the changes
> recently made to draft saving will have an idea what is going on here.
> 

Found the problem and I'm working on a solution: There are two (2) SPC
between the flag list and the internal date, but the spec only allows
for one.

Best,
  -- David

> best, Erik
> 
> -- 
> Sent from my free software system <http://fsf.org/>.
>