Gnus development mailing list
 help / color / mirror / Atom feed
From: JJ <ding_gnus.org@sumou.com>
To: ding@gnus.org
Subject: Debugging Emacs Gnus to determine the starttls command working with No Gnus
Date: Wed, 29 Sep 2010 11:59:13 -0400	[thread overview]
Message-ID: <9cba874b36d3f18d0f7d5446e59494cb@hcoop.net> (raw)

OK, I'm trying to accomplish the following:

I can use the git checkout of No Gnus no probs at home. At work, it
won't connect to hcoop.net's IMAP server. The admin has assured me that
port 993, and for that matter also 143, is not blocked at work.

I can connect however, without any change in setup, but using the Gnus
in Emacs 24, the latest bzr version.

I've checked I can't reach the server with `gnutls-cli -p imaps
mail.hcoop.net' which is the command that No Gnus uses at home to
connect. At work this just times out...

What I'd like to see is the actual commandline it the Emacs Gnus uses to
be able to connect to hcoop at work, since I just can't figure it out,
I've been experimenting today all day with various ports, nnimap-stream
variations and what have you, no luck...

However neither *imap-debug*, nor *nnimap-debug*, or *Messages* will
show me the commandline syntax the Emacs Gnus uses, so I can force No
Gnus to work that way.

I'm sure it's easy to derive, however don't know where to examine the
actual commandline syntax...
--
JJ





             reply	other threads:[~2010-09-29 15:59 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-29 15:59 JJ [this message]
2010-09-29 19:19 ` Lars Magne Ingebrigtsen
2010-10-06 14:33   ` JJ
2010-10-07 20:06     ` Lars Magne Ingebrigtsen
2010-10-20  9:25       ` JJ

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=9cba874b36d3f18d0f7d5446e59494cb@hcoop.net \
    --to=ding_gnus.org@sumou.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).