Re: trouble with smtp and authentication to an exchange server
- To: mutt-users@xxxxxxxx
- Subject: Re: trouble with smtp and authentication to an exchange server
- From: Kyle Wheeler <kyle-mutt@xxxxxxxxxxxxxx>
- Date: Thu, 26 Jun 2008 10:48:38 -0500
- Comment: DomainKeys? See http://domainkeys.sourceforge.net/
- Dkim-signature: v=1; a=rsa-sha1; c=relaxed; d=memoryhole.net; h=date :from:to:subject:message-id:references:mime-version:content-type :content-transfer-encoding:in-reply-to; s=default; bh=DeEhAg643w DR5fB4etYBY7iuhHY=; b=Kvmec/JNDyVNkgBU3ew48hwg0LQFIeTZvs5hag2t7S WjTc8HObfRUtkk1z7nrNvz39Xns7f/X3lVzZf94efFv1Rx5e2hGPARAF/NICv8OS LaLnfP8SlK8GXbcu4RW97dCmJ/hLDEz3zghjPqRXUPZOtbhWhZH0djax/zEDLBI3 U=
- Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=default; d=memoryhole.net; b=HLgbjCeY1YvG+8kXiFg3gcfpkVF2Lz0/uhq/oBFc2P+OI++zBqtLZ9L+DxFQE83oW1I2mzAUMbnZB5GEBN59W3+2bbTs6NCDflDpTF4bGedZyPAwrbZElJbnQEWB2hq6LNfeir7RNeahujQUQ79cZuX3b2vtQgN5LAyG2XRtq30=; h=Received:Received:Date:From:To:Subject:Message-ID:Mail-Followup-To:References:MIME-Version:Content-Type:Content-Disposition:Content-Transfer-Encoding:In-Reply-To:OpenPGP:User-Agent;
- In-reply-to: <20080626070652.GK1956@xxxxxx>
- List-post: <mailto:mutt-users@mutt.org>
- List-unsubscribe: send mail to majordomo@mutt.org, body only "unsubscribe mutt-users"
- Mail-followup-to: mutt-users@xxxxxxxx
- Openpgp: id=CA8E235E; url=http://www.memoryhole.net/~kyle/kyle-pgp.asc; preference=signencrypt
- References: <20080626070652.GK1956@xxxxxx>
- Sender: owner-mutt-users@xxxxxxxx
- User-agent: Mutt/1.5.18 (2008-06-02)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Thursday, June 26 at 09:06 AM, quoth Olaf Föllinger:
> I'm trying to send my mails to an exchange server and use
> authentication. First I've had problems to compile in SASL2 but
> found the solution here:
> http://marc.info/?l=mutt-dev&m=117752314512877&w=2. Now it compiles
> and starts fine. When it delivers the mail to the mail server it
> asks for the password and then fails with the message
>
> No authenticators available
>
> How can I further track the problem?
>
> Generally authentication works.
>
> telnet mail 25
> ...
> 250-AUTH GSSAPI NTLM LOGIN
> 250-AUTH=LOGIN
The reason it's printing that out is that is hasn't found any
authenticators that it supports. The next question, though, is: why?
Is it simply not recognizing which authenticators the server is
advertising? Is your version of SASL perhaps badly compiled (and/or
configured) and not support those authenticators? Is it simply not
handling failure well? I don't know which is the case for you. You can
try running mutt in debug-mode (-d 2) to find out (a debug-log will be
saved in ~/.muttdebug0). You can also try specifying which
authenticators to use by adding the following to your muttrc:
set smtp_authenticators="login"
~Kyle
- --
The greatest thing in family life is to take a hint when a hint is
intended---and not to take a hint when a hint isn't intended.
-- Robert Frost
-----BEGIN PGP SIGNATURE-----
Comment: Thank you for using encryption!
iEYEARECAAYFAkhjulYACgkQBkIOoMqOI16LcwCg7fbm6uxdK9kvlfVgoPVdx21O
AJYAoO2lqQ2dBnvVvLq3Br9yHYDFzGig
=5vAN
-----END PGP SIGNATURE-----