From: Steinar Bang <sb@dod.no>
To: ding@gnus.org
Subject: Re: nnimap with openssl stopping up after connecting in Windows
Date: Fri, 02 Jan 2009 08:59:04 +0100 [thread overview]
Message-ID: <uprj6xho7.fsf@dod.no> (raw)
In-Reply-To: <ur63meke2.fsf@torus.sehlabs.com>
>>>>> "Steven E. Harris" <seh@panix.com>:
> Check the value of `shell-file-name' in your Emacs instance. If, like
> me, you started Emacs from within a Cygwin shell,
Nope. At least not intentionally. My emacs is
GNU Emacs 22.3.1 (i386-mingw-nt6.0.6001) of 2008-09-06 on SOFT-MJASON
and is started from the start menu.
> this variable will bear a value such as "zsh". But try this:
> ,----
> | (let ((shell-file-name "C:/Program Files/emacs-22.3/bin/cmdproxy.exe"))
> | (gnus))
> `----
This is the value it already has unfortunally...:-/
`C-h v shell-file-name' gives:
shell-file-name is a variable defined in `C source code'.
Its value is
"C:/Program Files/emacs-22.3/bin/cmdproxy.exe"
[snip!]
> [Some time passes...]
> Well, maybe not. I still can't get this to work with STARTTLS, and now
> I'm noticing that even if I set `shell-file-name' back to "zsh",
> nnimap still works with openssl. If I include the form
> (nnimap-stream ssl)
That's also what I already have...:-/
(nnimap "myserver"
(nnimap-address "myserver.dyndns.org")
(nnimap-stream ssl))
> in my select method definition for the IMAP server, it works. Without
> that form, it tries to use STARTTLS, finds a Cygwin-compiled starttls
> program, and fails as described previously.
With ssl there it finds a SUA Community compiled openssl (since Cygwin
wouldn't install for me on Vista (with "the BLODA explanation" as the
closest I got).
http://www.suacommunity.com/
> I'd like to be more happy about this, but I'm confused.
So am I. Perhaps we don't have the same problem, even...? :-/
next prev parent reply other threads:[~2009-01-02 7:59 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-19 11:56 Vista, secure imap and firewalls? Steinar Bang
2008-11-19 17:37 ` Steinar Bang
2008-11-22 18:44 ` nnimap with openssl stopping up after connecting in Windows (Was: Vista, secure imap and firewalls?) Steinar Bang
2008-11-22 23:37 ` nnimap with openssl stopping up after connecting in Windows Steinar Bang
2008-11-24 9:12 ` Steinar Bang
2008-11-24 1:38 ` Steven E. Harris
2008-11-24 10:09 ` Simon Josefsson
2008-11-24 11:13 ` Steinar Bang
2008-12-11 20:46 ` When and how to look in ' *nnimap* ' buffers? (Was: nnimap with openssl stopping up after connecting in Windows) Steinar Bang
2008-12-21 18:34 ` nnimap with openssl stopping up after connecting in Windows Steinar Bang
2008-12-25 0:26 ` Steinar Bang
2008-12-26 11:21 ` Steinar Bang
2008-12-26 11:27 ` Steinar Bang
2008-12-26 13:13 ` Steinar Bang
2008-12-26 14:04 ` Steven E. Harris
2008-12-26 15:57 ` Steinar Bang
2008-12-26 17:25 ` Steinar Bang
2008-12-26 17:40 ` Steinar Bang
2008-12-31 13:06 ` Steinar Bang
2009-01-01 18:48 ` Steinar Bang
2008-12-26 14:12 ` Steven E. Harris
2008-12-26 15:58 ` Steinar Bang
2009-01-01 22:23 ` Steven E. Harris
2009-01-02 7:59 ` Steinar Bang [this message]
2009-01-02 13:10 ` Steven E. Harris
2009-01-02 13:37 ` Steinar Bang
2009-01-11 17:30 ` Steinar Bang
2009-01-11 18:04 ` Steinar Bang
2009-01-11 21:30 ` Reiner Steib
2009-01-12 8:41 ` Steinar Bang
2009-01-12 8:57 ` Steinar Bang
2009-01-15 12:43 ` Steinar Bang
2009-01-12 0:23 ` Steven E. Harris
2009-01-01 22:35 ` Steven E. Harris
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=uprj6xho7.fsf@dod.no \
--to=sb@dod.no \
--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).