Gnus development mailing list
 help / color / mirror / Atom feed
From: Pedro Silva <psilva@pedrosilva.pt>
To: ding@gnus.org
Subject: opening local nnimap server through shell stream fails at startup
Date: Wed, 08 May 2013 12:56:17 +0100	[thread overview]
Message-ID: <87ip2t4rdq.fsf@pedrosilva.pt> (raw)

When I first start gnus, the connection to a local IMAP server (dovecot)
via 'shell fails. It appears that 'nnimap-stream' is set to its default
'undecided', which means it first tries to use 'ssl, leading to the
following error:

--8<---------------cut here---------------start------------->8---
Unable to open server nnimap+dovecot due to: dovecot/993 System error
--8<---------------cut here---------------end--------------->8---

Of course, this doesn't happen when dovecot is listening on
localhost:993/ssl (but it *does* happen on localhost:143/network), but
I'd rather use the tunnel method.

Here is the relevant configuration:

--8<---------------cut here---------------start------------->8---
(add-to-list
 'gnus-secondary-select-methods '(nnimap "dovecot"
                                         (nnimap-address "localhost")
                                         (nnimap-stream shell)
                                         (nntp-authinfo-file "~/.authinfo.gpg")
                                         (nnimap-shell-program
					  "/usr/lib/dovecot/imap")
                                         (nnir-search-engine imap)))
--8<---------------cut here---------------end--------------->8---

I then go to the server buffer and close the connection, after which
opening it again works fine, although I tipically get one or more
duplicate {nnimap:dovecot} entries.

This might conceivably have something to do with the thread started
yesterday:

http://thread.gmane.org/op.wwpniicrgfp24t@nolsbang01.one.steria.dom

Any ideas on what's going on? Thanks for the help.
-- 
Pedro




                 reply	other threads:[~2013-05-08 11:56 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=87ip2t4rdq.fsf@pedrosilva.pt \
    --to=psilva@pedrosilva.pt \
    --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).