Re: possible imap.el bug

[Simon Josefsson <jas@extundo.com>]

"Ted Zlatanov" <tzz@lifelogs.com> writes:

> On Thu, 14 Oct 2004, jas@extundo.com wrote:
>
>> "Ted Zlatanov" <tzz@lifelogs.com> writes:
>> 
>>> I got this today while processing spam.  I'm not sure what the problem
>>> is, unfortunately, but it looks like some data may be missing from the
>>> overview?
>>>
>>> Ted
>>>
>>>
>>> Debugger entered--Lisp error: (wrong-type-argument stringp nil)
>>>   string-to-number(nil)
>>>   imap-message-copyuid-1("train")
>>>   imap-message-copy("111169" "train" dontcreate nil " *nnimap* depot")
>> 
>> Do (setq imap-log t) and get the last part from *imap-log*, it looks
>> like a protocol problem.
>
> The error may be due to something unusual in the message (a mail
> bounce here), so I'm attaching the headers of the bounce.  I've also
> seen this error happen with spam, which may also have funny headers.
> I edited the real address to nosuch@invalid.com.
...
> 10845 UID COPY 32361 "soccer".
> 10845 OK UID COPY completed.

Could you get the CAPABILITY line from that server too?  First lines
when connecting to the server.

The imap.el code check for the UIDPLUS capability (RFC 2359) and uses
some special code if present, and it is the code that crashes.  If the
server really supported UIDPLUS, the UID COPY response should be
something like:

A003 OK [COPYUID 4711] Done

If the capability line includes UIDPLUS, then this is a server bug.