Gnus development mailing list
 help / color / mirror / Atom feed
From: Jim Davidson <jdavidson@nospam.com>
Subject: Re: Using nnimap
Date: 24 Aug 2001 10:34:31 -0700	[thread overview]
Message-ID: <u8zg9nyzc.fsf@nospam.com> (raw)
In-Reply-To: <7zu1yxx6rr.fsf@amboise.ird.idealx.com>

jerome.marant@free.fr (Jérôme Marant) writes:

> Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann) writes:
> 
> > jerome.marant@free.fr (Jérôme Marant) writes:
> > 
> > >   I followed all what you adviced me to perform.
> > >   However, I guess I have to be able to enter the group if I want to 
> > >   get those buffers. As I could not enter the buffer, I got no
> > >   *imap-debug* and no *nnimap-debug*.  
> > 
> > Hm.  Hmmm...  And if you write the two setq statements in your ~/.gnus
> > and restart Emacs and Gnus?
> 
>   I've got the same result: *imap-debug* and *nnimap-debug* have not been
>   created ;(
> 
>   I've contacted my Internet provider and it would be better for
>   him to have IMAP logs in order to see what could be wrong in
>   IMAP messages.
> 
>   How can I get them?

You're confused.

Your Internet provider is not going to give you access to logs.  More
importantly, that's not where the problem lies; those buffers will be created
even if the IMAP server isn't working.  The problem is at your end,
and you need to debug your client to track it down.

If you've set the above variables, and restarted Emacs, then you need to step
through the relevant gnus functions, to see where things are going wrong.

You should put a break in gnus-server-opened.  Check that it's eventually
calling nnimap-server-opened.  Note that nnimap-server-opened will create the
*nnimap-debug* buffer, independent of whether the IMAP server can be
contacted.

Similarly, you should get to gnus-open-server and then nnimap-open-server,
which will actually attempt to open the connection.  By now both the
debug buffers should have lots of information in them.

Again, this is independent of whether the IMAP server can be contacted.

-- 
Jim Davidson
jdavidson @ acm.org



  reply	other threads:[~2001-08-24 17:34 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-19 18:02 Jérôme Marant
2001-08-19 16:25 ` Kai Großjohann
2001-08-19 16:42   ` Jérôme Marant
2001-08-19 22:59     ` Kai Großjohann
2001-08-21  8:01       ` Jérôme Marant
2001-08-21  9:29         ` Kai Großjohann
2001-08-21  9:57           ` Jérôme Marant
2001-08-21 12:12             ` Kai Großjohann
2001-08-21 12:32               ` Jérôme Marant
2001-08-21 13:11             ` Kai Großjohann
2001-08-22  7:44               ` Jérôme Marant
2001-08-22  8:51                 ` Simon Josefsson
2001-08-23  7:52                   ` Jérôme Marant
2001-08-22 19:22                 ` Kai Großjohann
2001-08-23  7:58                   ` Jérôme Marant
2001-08-23 15:52                     ` Kai Großjohann
2001-08-24  7:21                       ` Jérôme Marant
2001-08-24 17:34                         ` Jim Davidson [this message]
2001-08-24 23:35                           ` Jérôme Marant
2001-08-24 21:48                             ` Simon Josefsson
2001-08-25 17:32                             ` Roland Mas
2001-08-25 17:47                               ` Simon Josefsson
2001-08-27 17:37                             ` Jim Davidson
2001-08-21 15:08           ` Jody Klymak
2001-08-21 15:52             ` Kai Großjohann
  -- strict thread matches above, loose matches on Subject: below --
2000-03-07 18:06 using nnimap Arcady Genkin
2000-03-07 19:41 ` Simon Josefsson

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=u8zg9nyzc.fsf@nospam.com \
    --to=jdavidson@nospam.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).