From: Steinar Bang <sb@dod.no>
To: ding@gnus.org
Subject: Problems running IMAP over ssh port forwarding
Date: Mon, 27 Feb 2017 10:23:48 +0100 [thread overview]
Message-ID: <upzc4lzg2di3.fsf@dod.no> (raw)
Platform: Windows 7,
GNU Emacs 24.4.1 (i686-pc-mingw32) of 2014-10-24 on LEG570
Ma Gnus v0.16 (last standalone git version)
I tried setting up a port forwarding like so:
ssh -L 143:localhost:143 mysever.mydomain
I then tried setting the IMAP server like this:
(setq gnus-secondary-select-methods
'((nnimap "privat"
(nnimap-address "localhost")
(nnimap-authenticator cram-md5)
(nnimap-server-port 143))
))
However this doesn't work. In the " *nnimap localhost 143 **nntpd*"
buffer, I saw the following (replaced CR with explicit "^M" to be able
to send it in this message):
[CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE IDLE STARTTLS AUTH=PLAIN AUTH=CRAM-MD5] Dovecot ready.^M
BAD CR sent without LF^M
* BAD Error in IMAP command received by server.^M
* BAD Error in IMAP command received by server.^M
* BYE Too many invalid IMAP commands.^M
Process *nnimap* connection broken by remote peer
Does anyone have an idea what could be wrong here?
Thanks!
- Steinar
next reply other threads:[~2017-02-27 9:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-27 9:23 Steinar Bang [this message]
2017-02-27 21:50 ` Malcolm Purvis
2017-02-28 6:39 ` Steinar Bang
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=upzc4lzg2di3.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).