From: Simon Josefsson <jas@extundo.com>
Cc: ding@gnus.org
Subject: Re: [nnimap] Is `A T' supposed to work with nnimap backend
Date: Thu, 20 Nov 2003 05:40:59 +0100 [thread overview]
Message-ID: <ilu7k1vbqjo.fsf@latte.josefsson.org> (raw)
In-Reply-To: <m3n0arfzci.fsf@newsguy.com> (Harry Putnam's message of "Wed, 19 Nov 2003 22:17:17 -0600")
Harry Putnam <reader@newsguy.com> writes:
> Simon Josefsson <jas@extundo.com> writes:
>
>> No. What happens? What does *imap-log* contain (after toggling
>> imap-log)?
>
> How does one toggle an imap-log.
> An `s' search on entire gnus inof shows no hits on imap-log.
I added the following, comments appreciated.
Debugging IMAP
--------------
IMAP is a complex protocol, at least compared to NNTP or POP3. Perhaps
for that reason, implementation bugs are not unlikely. If you
encounter an 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 reading the protocol
dump of the exchanges between Gnus and the server. Even if you are not
familiar with network protocols, including the protocol exchange in
IMAP-related bug reports may be critical for solving the problem.
Because this protocol dump generate potentially large buffers, it is
not enabled by default. You can enable it by toggling `imap-log' as
follows:
(setq imap-log t)
This instruct the `imap.el' package to dump sent to the server, and
everything received from the server. The output is stored in the
buffer `*imap-log*'. Look for error messages, which sometimes are
tagged with the keyword `BAD'.
next prev parent reply other threads:[~2003-11-20 4:40 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 [this message]
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
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=ilu7k1vbqjo.fsf@latte.josefsson.org \
--to=jas@extundo.com \
--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).