Re: Fetching Problems

[Simon Josefsson <jas@pdc.kth.se>]

Jake Colman <colman@ppllc.com> writes:

> Here it is.  I did a 'g', split the messages, and there's one left
> in my INBOX still unread.  By the way, if I subscribe to MAIL/INBOX
> and try to read this message via nnimap, I am told that the message
> has been cancelled and I cannot read it.

Ok, that and this part explains it:

> ======================================================================
> 1 -> nnimap-request-scan: group="INBOX/Personal/Pegg" server="truman"
...
> | | 3 -> nnimap-request-head: article=25377 group=nil server=nil to-buffer=nil
> | | | 4 -> nnimap-request-article-part: part=RFC822\.HEADER article=25377 group=nil server=nil to-buffer=nil add-peek=nil
> | | | | 5 -> nnimap-possibly-change-group: group=nil server=nil
> | | | | | 6 -> nnimap-possibly-change-server: server="truman"
> | | | | | | 7 -> nnimap-open-server: server="truman" defs=nil
> | | | | | | | 8 -> nnimap-server-opened: server="truman"
> | | | | | | | 8 <- nnimap-server-opened: (open run)
> | | | | | | 7 <- nnimap-open-server: t
> | | | | | 6 <- nnimap-possibly-change-server: t
> | | | | 5 <- nnimap-possibly-change-group: "INBOX"
> | | | 4 <- nnimap-request-article-part: nil
> | | 3 <- nnimap-request-head: nil
                                ^^

Nnimap wasn't enable to fetch the article headers it wanted to look
at, for some strange reason, so the entire splitting failed.

Ok, to find out why it couldn't fetch the article headers (nnimap
shouldn't just silently ignore that) could you kill *imap-log* and
*nnimap-debug*, enter your server buffer (`^'), request a split (`s')
on your nnimap backend, and mail me both debug buffers?

/s