From: Steinar Bang <sb@dod.no>
To: ding@gnus.org
Subject: Re: nnimap with openssl stopping up after connecting in Windows
Date: Mon, 24 Nov 2008 10:12:45 +0100 [thread overview]
Message-ID: <87ej11jxma.fsf@hjemme.hjemme.lan> (raw)
In-Reply-To: <uprkncoxv.fsf@dod.no>
>>>>> Steinar Bang <sb@dod.no>:
> Setting imap-log to t, I find the following in the *imap-log* buffer
> (I've replaced CR characters with the string "^M" to preserve them in
> this posting, I've also anonymized server and domain names):
> depth=0 /O=Dovecot mail server/OU=myserver/CN=myserver/emailAddress=root@myserver.mydomain.no
> verify error:num=18:self signed certificate
> verify return:1
> depth=0 /O=Dovecot mail server/OU=myserver/CN=myserver/emailAddress=root@myserver.mydomain.no
> verify return:1
> * OK Dovecot ready.^M
> 6 NOOP^M
> * BYE Disconnected for inactivity.^M
> read:errno=0
> 7 CAPABILITY^M
[snip!]
> Or perhaps what we have is CRCRLF, where only the first CR is visible?
When I look at this like Steven did, ie. using hexl-mode, I see that this is the
case.
All lines where the "^M" show have the sequence "0d0d0a" (CRCRLF),
while the lines without an "^M" have "0d0a" (CRLF).
Note: I'm using SUA openssl, not the cygwin one (but the behaviour
seems to be identical).
next prev parent reply other threads:[~2008-11-24 9:12 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 [this message]
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
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=87ej11jxma.fsf@hjemme.hjemme.lan \
--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).