This repository has been archived by the owner. It is now read-only.

Mutt "No Authenticators Available" yosemite #33419

Closed
jonmorehouse opened this Issue Oct 21, 2014 · 37 comments

Comments

Projects
None yet
@jonmorehouse
Copy link
Contributor

jonmorehouse commented Oct 21, 2014

I'm having an issue sending email with mutt from Yosemite. My mail fetching works, but whenever I attempt to send an email I'm getting the error message "No Authenticators Found". Has anyone else seen this regression after installing yosemite?

@pdweinstein

This comment has been minimized.

Copy link

pdweinstein commented Oct 21, 2014

I have also seen this issue post Yosemite update trying to send via Gmail SMTP

@jonmorehouse jonmorehouse changed the title Mutt "No Authenticators Found" yosemite Mutt "No Authenticators Available" yosemite Oct 21, 2014

@Bocard23

This comment has been minimized.

Copy link

Bocard23 commented Oct 21, 2014

I had/have the same issue. Gave up at some point..

@heytrav

This comment has been minimized.

Copy link

heytrav commented Oct 22, 2014

Also have this issue since updating to Yosemite.

@chdiza

This comment has been minimized.

Copy link
Contributor

chdiza commented Oct 22, 2014

I do not have this issue in Yosemite.

@chdiza

This comment has been minimized.

Copy link
Contributor

chdiza commented Oct 22, 2014

Maybe try two things (separately): (1) Comment out the "with-gss" in the formula and re-brew; (2) try building from HEAD (there was recently some patch to the sasl code).

@jonmorehouse

This comment has been minimized.

Copy link
Contributor Author

jonmorehouse commented Oct 22, 2014

I tried the two steps above to no avail, after surfing around the net, it looks like the only solution is to either a.) use macports and run an outdated mutt version or b.) use msmtp or some other sending mechanism other than the built in mutt system for sending emails.

I wrote a blog post here detailing how to set up mutt with msmtp http://jonmorehouse.tumblr.com/post/100650456885/mutt-gmail-on-osx-yosemite

@rprimus

This comment has been minimized.

Copy link
Contributor

rprimus commented Oct 22, 2014

I have just run into this problem. Adding the following to .muttrc:

set smtp_authenticators = 'gssapi:login'

has worked for me.

@lukevers

This comment has been minimized.

Copy link

lukevers commented Oct 22, 2014

Along with @rprimus, adding that to .muttrc did it! I'm not sure this should be open as a Homebrew issue though.

@prlysophie

This comment has been minimized.

Copy link

prlysophie commented Oct 22, 2014

Thanks a million @rprimus for solving an issue that has been irritating me for days now--works great.

@chdiza

This comment has been minimized.

Copy link
Contributor

chdiza commented Oct 22, 2014

There is already a thread about this issue on the mutt mailing list.

@fergusb

This comment has been minimized.

Copy link

fergusb commented Oct 23, 2014

Kudos to @rprimus

@mistydemeo

This comment has been minimized.

Copy link
Member

mistydemeo commented Oct 23, 2014

Could you link the thread, please? Thanks!

@chdiza

This comment has been minimized.

@mistydemeo

This comment has been minimized.

Copy link
Member

mistydemeo commented Oct 23, 2014

Thanks!

@chdiza

This comment has been minimized.

Copy link
Contributor

chdiza commented Oct 23, 2014

On my machine I have a Mav partition ("Macintosh_HD") and a Yosemite partition ("/"). On each, I used find to search for anything with "*gssapi*" in the path (case-insensitive). After filtering out some false positives (like perl man pages and such), I have found a difference that could be relevant.

On Mavericks, there exists:

/volumes/Macintosh_HD/usr/lib/sasl2/libgssapiv2.la
/volumes/Macintosh_HD/usr/lib/sasl2/openldap/libgssapiv2.2.so
/volumes/Macintosh_HD/usr/lib/sasl2/openldap/libgssapiv2.la

While on Yosemite there is:

/usr/lib/sasl2/openldap/libgssapiv2.2.so

In other words, something is present on Mavericks that isn't on Yosemite, namely, the *.la file (The latter occurrence of it is a symlink to the former). I have zero expertise, so I don't know if this is behind the problem, but it seemed relevant.

@chdiza

This comment has been minimized.

Copy link
Contributor

chdiza commented Oct 23, 2014

Running mutt in debug mode (level 5) shows this:

[2014-10-23 13:35:22] SASL: Parameter Error in /SourceCache/passwordserver_saslplugins/passwordserver_saslplugins-183/plain_clienttoken.c near line 195
[2014-10-23 13:35:22] smtp_auth_sasl: PLAIN-CLIENTTOKEN unavailable
[2014-10-23 13:35:22] No authenticators available
@Bocard23

This comment has been minimized.

Copy link

Bocard23 commented Oct 25, 2014

thank you @rprimus, your solution worked for me as well.

@marvi

This comment has been minimized.

Copy link

marvi commented Oct 25, 2014

Thank you @rprimus Works fine here.

@lush

This comment has been minimized.

Copy link

lush commented Nov 14, 2014

@rprimus: works perfect, thanks.

@gusennan

This comment has been minimized.

Copy link
Contributor

gusennan commented Nov 17, 2014

Is this a home-brew issue or a mutt issue?

@chdiza

This comment has been minimized.

Copy link
Contributor

chdiza commented Nov 17, 2014

Is this a home-brew issue or a mutt issue?

It's not a homebrew issue; it is either a mutt issue or an OSX issue, and I strongly suspect it's the latter. When the mutt devs pronounce on whether this workaround is really the right thing to do, I'll report back here.

@jacknagel

This comment has been minimized.

Copy link
Contributor

jacknagel commented Dec 24, 2014

Closing since the conclusion seems to be that Homebrew can't address this.

@jacknagel jacknagel closed this Dec 24, 2014

scanf pushed a commit to scanf/dotfiles that referenced this issue Jan 1, 2015

Alexander Alemayhu
Mutt and GPG changes.
o Remove . prefix for mutt configuration.
o Copy over mutt files.
o Add template file for passwords.
o For some reason[0] I need this line.
o Ensure gpg-agent is present.

[0]: Homebrew/legacy-homebrew#33419
@tricon

This comment has been minimized.

Copy link

tricon commented Jan 8, 2015

@rprimus 👍

@mcansky

This comment has been minimized.

Copy link

mcansky commented Jan 14, 2015

@rprimus ' solution worked for me too (yosemite, fresh homebrew install of mutt, gmail), thanks !

@lvnilesh

This comment has been minimized.

Copy link

lvnilesh commented Jan 17, 2015

Thanks @rprimus mutt worked and issue resolved when I added this to my ~/.muttrc

set smtp_authenticators = 'gssapi:login'
@chdiza

This comment has been minimized.

Copy link
Contributor

chdiza commented Jan 23, 2015

The variable $smtp_authenticators provides a list of authenticating mechanisms that mutt will attempt to use, in order, from left to right.

For gmail (which is the only place I've run into the issue that started this thread), mutt on my machine with the @rprimus solution in place cannot use gssapi, so it moves on to login. I noticed this by running mutt in debug mode and looking at the logs. The @rprimus solution, at least on my machine, can be shortened to just 'login' rather than 'gssapi:login'.

As long as 'login' makes it into $smtp_authenticators, mutt should eventually land on it. For example, I tried sasl:gssapi:cram-md5:login, and mutt briefly flashed that it couldn't use cram-md5 before successfully sending a message. Inspection of debug logs revealed that it tried all three of the methods listed before login and none of them worked.

@5202

This comment has been minimized.

Copy link

5202 commented Feb 25, 2015

Thank you @rprimus .. after searching four hours, this worked!

@drbob830

This comment has been minimized.

Copy link

drbob830 commented Apr 24, 2015

Thanks @primus.

@drbob830

This comment has been minimized.

Copy link

drbob830 commented Apr 24, 2015

It affected me on Maverick as well as Yosemite. after a brew mutt install. I think its a brew issue, not Yosemite, but I'm certainly not sure.

@chdiza

This comment has been minimized.

Copy link
Contributor

chdiza commented Apr 24, 2015

I think its a brew issue, not Yosemite, but I'm certainly not sure.

It's not a brew issue. I don't brew mutt but I do see this issue. I can reproduce in 10.10 on non-brewed mutt. Also, I used to not be able to reproduce it on 10.9 with a non-brewed mutt about 6 months ago; things might be different now after the ensuing Security Updates to Mavericks, I haven't yet tried.

@drbob830

This comment has been minimized.

Copy link

drbob830 commented Apr 24, 2015

Thanks
Bob

On Fri, Apr 24, 2015 at 06:56:51AM -0700, chdiza wrote:

I think its a brew issue, not Yosemite, but I'm certainly not sure.

It's not a brew issue. I don't brew mutt but I do see this issue. I can reproduce in 10.10 on non-brewed mutt. Also, I used to not be able to reproduce it on 10.9 with a non-brewed mutt about 6 months ago; things might be different now after the ensuing Security Updates to Mavericks, I haven't yet tried.


Reply to this email directly or view it on GitHub:
#33419 (comment)

@dlo

This comment has been minimized.

Copy link
Contributor

dlo commented May 15, 2015

Thanks @rprimus! Appreciate you posting here. Your solution did it for me as well.

@maxx

This comment has been minimized.

Copy link

maxx commented Jun 7, 2015

set smtp_authenticators = 'gssapi:login'
..was actually really slow for me ..
smtp_authenticators = 'login'

also did the trick, but is much faster.

using gssapi:login caused a long delay while mutt printed "TLSv1.2 connection using TLSv1/SSLv3 (ECDHE-RSA-AES128-GCM-SHA256)"

@chdiza

This comment has been minimized.

Copy link
Contributor

chdiza commented Jun 7, 2015

@maxx Good to have confirmation of #33419 (comment).

@jingkungao

This comment has been minimized.

Copy link

jingkungao commented Jun 19, 2015

Thanks @rprimus , this works for me!

@arapov

This comment has been minimized.

Copy link

arapov commented Jul 7, 2015

works for me.

@mntnman

This comment has been minimized.

Copy link

mntnman commented Jan 7, 2016

And it still works with El Capitan! Thanks much!

@Homebrew Homebrew locked and limited conversation to collaborators Feb 17, 2016

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.