From: asjo@koldfront.dk (Adam Sjøgren)
To: ding@gnus.org
Subject: Re: allow GSSAPI for imap access
Date: Mon, 22 Feb 2016 08:27:37 +0100 [thread overview]
Message-ID: <87k2lxkxw6.fsf@tullinup.koldfront.dk> (raw)
In-Reply-To: <83vb5pvn8o.fsf@jochen.org>
Jochen writes:
> If there are, get a kerberos ticket and try "imtest -m gssapi -p imap
> <hostname>" or "gsasl <hostname> imap --mechanism GSSAPI".
Unfortunately it didn't work:
$ imtest -m gssapi -p imap SERVER
S: * OK Microsoft Exchange Server 2007 IMAP4 service ready
C: C01 CAPABILITY
S: * CAPABILITY IMAP4 IMAP4rev1 AUTH=NTLM AUTH=GSSAPI LOGINDISABLED STARTTLS IDLE NAMESPACE LITERAL+
S: C01 OK CAPABILITY completed.
Authentication failed. no mechanism available
Security strength factor: 0
and:
$ gsasl SERVER imap --mechanism GSSAPI
Trying ‘SERVER’...
* OK Microsoft Exchange Server 2007 IMAP4 service ready
. CAPABILITY
* CAPABILITY IMAP4 IMAP4rev1 AUTH=NTLM AUTH=GSSAPI LOGINDISABLED STARTTLS IDLE NAMESPACE LITERAL+
. OK CAPABILITY completed.
. STARTTLS
. OK Begin TLS negotiation now.
. CAPABILITY
* CAPABILITY IMAP4 IMAP4rev1 AUTH=NTLM AUTH=GSSAPI AUTH=PLAIN IDLE NAMESPACE LITERAL+
. OK CAPABILITY completed.
. AUTHENTICATE GSSAPI
+
error: server did not return a token
Probably something on the Microsoft Exchange-side...
Best regards,
Adam
--
"I used to feel Emacs' way strange. Maybe updating Adam Sjøgren
the copyright years of Walt Disney's works every year asjo@koldfront.dk
is nonsense. But Emacs' way is alike to it."
next prev parent reply other threads:[~2016-02-22 7:27 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-14 16:07 Jochen Hein
2016-02-14 16:07 ` [PATCH 1/4] open-gssapi-stream: remove parameter user Jochen Hein
2016-02-14 16:07 ` [PATCH 2/4] network-stream: allow type gssapi Jochen Hein
2016-02-14 16:07 ` [PATCH 3/4] nnimap: handle imap connections with type 'gssapi Jochen Hein
2016-02-14 16:07 ` [PATCH 4/4] update nnimap documentation for gssapi connections Jochen Hein
2016-02-15 7:59 ` allow GSSAPI for imap access Lars Ingebrigtsen
2016-02-15 14:35 ` Adam Sjøgren
2016-02-15 16:39 ` Jochen Hein
2016-02-15 17:29 ` Adam Sjøgren
2016-02-15 18:31 ` Jochen Hein
2016-02-15 18:56 ` Adam Sjøgren
2016-02-15 19:58 ` Jochen Hein
2016-02-22 7:27 ` Adam Sjøgren [this message]
2016-02-22 18:41 ` Jochen Hein
2016-02-23 12:52 ` Adam Sjøgren
2016-02-15 14:38 ` Hein, Jochen
2016-02-15 14:46 ` Lars Ingebrigtsen
2016-02-16 5:57 ` Lars Ingebrigtsen
2016-02-16 9:21 ` Hein, Jochen
2016-02-21 3:10 ` Lars Ingebrigtsen
2016-03-20 19:11 ` Jochen Hein/Jochen Kellner
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=87k2lxkxw6.fsf@tullinup.koldfront.dk \
--to=asjo@koldfront.dk \
--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).