From: Ted Zlatanov <tzz@lifelogs.com>
Subject: Re: [nnimap] Is `A T' supposed to work with nnimap backend
Date: Thu, 20 Nov 2003 08:48:20 -0500 [thread overview]
Message-ID: <4nhe0zjgm3.fsf@lockgroove.bwh.harvard.edu> (raw)
In-Reply-To: <ilu7k1vbqjo.fsf@latte.josefsson.org> (Simon Josefsson's message of "Thu, 20 Nov 2003 05:40:59 +0100")
Here's my version.
Debugging IMAP
--------------
IMAP is a complex protocol, more so than NNTP or POP3. Implementation
bugs are not unlikely, and we do our best to fix them right away. If
you encounter odd behaviour, chances are that either the server or
Gnus is buggy.
If you are familiar with network protocols in general, you will
probably be able to extract some clues from the protocol dump of the
exchanges between Gnus and the server. Even if you are not familiar
with network protocols, when you include the protocol dump in
IMAP-related bug reports you are helping us with data critical to
solving the problem. Therefore, we strongly encourage you to include
the protocol dump when reporting IMAP bugs in Gnus.
Because the protocol dump, when enabled, generates lots of data, it is
disabled by default. You can enable it by toggling `imap-log' as
follows:
(setq imap-log t)
This instructs the `imap.el' package to log any exchanges with the
server. The log is stored in the buffer `*imap-log*'. Look for
error messages, which sometimes are tagged with the keyword `BAD' -
but when submitting a bug, make sure to include all the data.
next prev parent reply other threads:[~2003-11-20 13:48 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-19 16:56 Harry Putnam
2003-11-20 3:31 ` Simon Josefsson
2003-11-20 4:17 ` Harry Putnam
2003-11-20 4:40 ` Simon Josefsson
2003-11-20 10:54 ` Harry Putnam
2003-11-20 11:57 ` Simon Josefsson
2003-11-20 12:21 ` Harry Putnam
2003-11-20 12:30 ` Simon Josefsson
2003-11-20 13:48 ` Ted Zlatanov [this message]
2003-11-20 14:23 ` Derrell.Lipman
2003-11-20 14:24 ` Simon Josefsson
2003-11-20 16:19 ` Ted Zlatanov
2003-11-20 4:20 ` Harry Putnam
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=4nhe0zjgm3.fsf@lockgroove.bwh.harvard.edu \
--to=tzz@lifelogs.com \
/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).