Re: [nnimap] Is `A T' supposed to work with nnimap backend

[Harry Putnam <reader@newsguy.com>]

Simon Josefsson <jas@extundo.com> writes:

> 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.

Good addition Simon.  What you posted was probably not the final version 
but I've added a few spelling/grammer  changes as noted.  The
substance seems good as it stands.

> 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
                                ^^^^^^^^
                                generates       
> 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
          ^^^^^^^^                               ^ 
          instructs                           everthing
> 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'.