Re: How to debug a new IMAP server type?

[Steinar Bang <sb@dod.no>]

>>>>> Lars Ingebrigtsen <larsi@gnus.org>:

>> What buffers do I look in? What do I look for in those buffers? Are
>> there debug options to switch on?

> " *imap log*"

If I understand it correctly, It seems to be fetching information for
just a single article (UID 2017), this is from entering the davmail
INBOX:
21:06:04 [localhost] 41 SELECT "INBOX"
21:06:06 [localhost] 42 SELECT "INBOX"
21:06:10 [localhost] 43 UID FETCH 2017 (UID RFC822.SIZE BODYSTRUCTURE BODY.PEEK[HEADER.FIELDS (Subject From Date Message-Id References In-Reply-To Xref X-Diary-Time-Zone X-Diary-Dow X-Diary-Year X-Diary-Month X-Diary-Dom X-Diary-Hour X-Diary-Minute To Newsgroups Cc)])

For comparison, here is entering an nnimap group on my dovecot server:
21:09:56 [imap.mydomain.com] 46 SELECT "INBOX"
21:09:56 [imap.mydomain.com] 47 SELECT "INBOX"
21:09:56 [imap.mydomain.com] 48 UID FETCH 1:2,52,551:557,561:562,564:567,570,572,584:585,609,652,655,658:669,686,791,798:801,805,836,1005:1006,1023:1024,1053,1058,1068,1084,1088,1090:1094,1097,1099:1100,1104,1110,1116,1127,1197,1204,1206,1209,1225:1226,1254,1262,1280,1284,1313,1331,1341,1347:1348,1350,1417,1441,1443,1447,1451,1485,1489,1493,1539,1554,1576,1592,1594 (UID RFC822.SIZE BODYSTRUCTURE BODY.PEEK[HEADER.FIELDS (Subject From Date Message-Id References In-Reply-To Xref X-Diary-Time-Zone X-Diary-Dow X-Diary-Year X-Diary-Month X-Diary-Dom X-Diary-Hour X-Diary-Minute To Newsgroups Cc)])

> and " *nnimap ... *" buffers.
  
The " *nnimap localhost 1143  *nntpd**" buffer seems to contain the
email I see when I selet the single article I see in the Summary.

Then it ends with:
* BYE Closing connection

Process *nnimap*<1> connection broken by remote peer

Is that significant?

Then there is also the buffer " *nnimap localhost 1143  *nntpd**-398832"
with the following content:
211 2017 Article retrieved.
Chars: 28785
Lines: 6
From: John Doe <john.doe@somecompany.no>
To: Steinar BANG <steinar.bang@somecompany.no>
Date: Tue, 21 Jan 2014 08:13:04 +0100
Subject: SV: Hjemme med sykt barn
Message-ID: <701DABD47A1A7044999B70D8862952E339DA8A8829@SVVEPOST01.somecompany.no>
References: <82a64bae86d240bf9076e8263d6fd2dc@DB3PR07MB092.eurprd07.prod.outlook.com>
In-Reply-To: <82a64bae86d240bf9076e8263d6fd2dc@DB3PR07MB092.eurprd07.prod.outlook.com>
)
55 OK UID FETCH completed
* BYE Closing connection

Process *nnimap*<1> connection broken by remote peer
.

(in fact there seems to be a new such buffer, with an "-somenumber"
extension, created every time I enter the INBOX, or when I try to
display the single article.

And they are never cleaned up as far as I can tell.

> Stepping trough `nnimap-transform-headers' might also help.

It stepped through the while loop in the function once (which by now
isn't too surprising, there seems to be only one article seen by this
point in time).

It does what it's supposed to do with the single article it has to work
with, and what's left at the end, is this:
211 2017 Article retrieved.
Chars: 28785
Lines: 6
From: John Doe <john.doe@somecompany.no>
To: Steinar BANG <steinar.bang@somecompany.no>
Date: Tue, 21 Jan 2014 08:13:04 +0100
Subject: SV: Hjemme med sykt barn
Message-ID: <701DABD47A1A7044999B70D8862952E339DA8A8829@SVVEPOST01.somecompany.no>
References: <82a64bae86d240bf9076e8263d6fd2dc@DB3PR07MB092.eurprd07.prod.outlook.com>
In-Reply-To: <82a64bae86d240bf9076e8263d6fd2dc@DB3PR07MB092.eurprd07.prod.outlook.com>
)
70 OK UID FETCH completed
* BYE Closing connection

Process *nnimap*<1> connection broken by remote peer
.

And from that it should have been able to at least display meaningful
information from that article, rather than what it displays, which is
this: 
  O. [   ?: nobody                 ] (none)

Here is the summary line for the article two articles earlier in the thread:
? +    [  21: Steinar Bang           ] How to debug a new IMAP server type?

So there should have been a line number (which is present in the headers
left in the " *nnimap..." buffer), and there should have been the real
name of the sender (which is also present in From: header left in the "
*nnimap..." buffer), and there should have been a subject (which is also
present in the leftover headers in the " *nnimap..." buffer).

As far as I can tell the headers all have the correct form.

Is it the "* BYE" and the closing connection message that is confusing
the stuff that is trying to display the summary?