From: Steinar Bang <sb@dod.no>
To: ding@gnus.org
Subject: How to debug a new IMAP server type?
Date: Sat, 18 Jan 2014 18:58:35 +0100 [thread overview]
Message-ID: <87ob392mus.fsf@dod.no> (raw)
In-Reply-To: <87zjnb8nqx.fsf@dod.no>
How do one go about debugging a new IMAP server type?
What buffers do I look in? What do I look for in those buffers? Are
there debug options to switch on?
What I've done so far, is to use WireShark and also trying to step
through entering a group on the server in edebug. Neither of these has
made me any wiser.
As far as I can tell from the WireShark grab, there is a seemingly OK
IMAP dialog between Gnus and the server. But the result in Gnus is
rather disappointing, A single article shows up in the summary, looking
like this:
O. [ ?: nobody ] (none)
Entering that article displays an article that looks OK, and looks like
it could be the article in question, based on the time it was sent.
(The server in question is davmail, running on a debian testing machine)
next prev parent reply other threads:[~2014-01-18 17:58 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-04 21:01 davmail and nnimap issues Steinar Bang
2014-01-18 17:58 ` Steinar Bang [this message]
2014-01-30 0:27 ` How to debug a new IMAP server type? Lars Ingebrigtsen
2014-01-30 21:16 ` Steinar Bang
2014-01-30 22:06 ` Lars Ingebrigtsen
2014-01-31 0:02 ` Steinar Bang
2014-01-31 0:04 ` Lars Ingebrigtsen
2014-01-31 7:02 ` Steinar Bang
2014-01-31 7:31 ` Lars Ingebrigtsen
2014-01-31 17:50 ` Steinar Bang
2014-02-19 13:49 ` Was the davmail fix synced to emacs bzr? (Was: How to debug a new IMAP server type?) Steinar Bang
2014-03-05 14:09 ` Was the davmail fix synced to emacs bzr? Lars Ingebrigtsen
2014-03-05 14:16 ` Steinar Bang
2014-03-05 15:15 ` Lars Ingebrigtsen
2014-03-06 21:49 ` Steinar Bang
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87ob392mus.fsf@dod.no \
--to=sb@dod.no \
--cc=ding@gnus.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).