Gnus development mailing list
 help / color / mirror / Atom feed
From: Steinar Bang <sb@dod.no>
To: ding@gnus.org
Subject: Re: nnimap with openssl stopping up after connecting in Windows
Date: Fri, 26 Dec 2008 18:25:34 +0100	[thread overview]
Message-ID: <ud4fec0hd.fsf@dod.no> (raw)
In-Reply-To: <ulju3aq0g.fsf@dod.no>

>>>>> Steinar Bang <sb@dod.no>:

> Right.  I'd thought I'd heard about 'binary somewhere.  But it wasn't
> on the list, so I thought I'd imagined that.  I'll try using that in
> my experiment.

> That is: I'll try 'undecided first to see what happens.  I'm also
> planning on trying out 'undecided-unix to emulate the behaviour on
> unix platforms.

Calling set-buffer-process-coding-system fails, even when just calling it in
imap-open.  So that's probably not the right thing either.

It fails with the 
 Unable to open server nnimap+myserver due to: No process
message.

So I'll try set-buffer-file-coding-system 'undecided-unix and 'binary
(I've already tried 'undecided without any effect), but I'm not holding
my breath, since this looks like it's related to saving and loading
files, and there is no such thing taking place in the nnimap buffers...




  reply	other threads:[~2008-12-26 17:25 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 [this message]
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=ud4fec0hd.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).