[arch-general] Mutt - no authenticators available
Hi I have been trying for hours but cant get mutt working. I used configuration from different forums. They all made sense but neither work. Also, the mutt package availabe in official arch repo has no debugging support so I couldn't figure out what was going wrong. After some internet research and keen eyes on mutt's on-screen logs, I found that mutt was trying to authenticate plainly. Then I learnt about authenticators. I enabled these authenticators: set imap_authenticators=”digest-md5:gssapi:cram-md5:login” set smtp_authenticators=”digest-md5:gssapi:cram-md5:login” And now I am exhausted and , quite frankly, frustrated. The only logs generated by journalctl are: Feb 25 10:44:15 ARCH mutt[31322]: GSSAPI client step 1 Feb 25 10:44:37 ARCH mutt[31322]: DIGEST-MD5 common mech free Feb 25 10:45:04 ARCH mutt[31328]: GSSAPI client step 1 Feb 25 10:45:06 ARCH mutt[31328]: DIGEST-MD5 common mech free Feb 25 10:45:10 ARCH mutt[31329]: GSSAPI client step 1 Feb 25 10:45:12 ARCH mutt[31329]: DIGEST-MD5 common mech free Feb 25 10:45:40 ARCH mutt[31332]: DIGEST-MD5 common mech free Feb 25 10:48:29 ARCH mutt[31404]: DIGEST-MD5 common mech free Feb 25 10:48:45 ARCH mutt[31406]: GSSAPI client step 1 Feb 25 10:49:18 ARCH mutt[31406]: DIGEST-MD5 common mech free Feb 25 10:50:18 ARCH mutt[31421]: DIGEST-MD5 common mech free Feb 25 10:53:46 ARCH mutt[31530]: GSSAPI client step 1 Feb 25 10:53:49 ARCH mutt[31530]: DIGEST-MD5 common mech free FYI I have 'cyrus-sasl' and 'cyrus-sasl-gssapi' packages installed. My .muttrc: set imap_authenticators=”gssapi:digest-md5:cram-md5:login” set smtp_authenticators=”gssapi:digest-md5:cram-md5:login” set imap_user = “myemail@hotmail.com” set imap_pass = “mypassword" set smtp_url = smtp://smtp-mail.outlook.com:465 // Earlier, I tried port 587 set smtp_pass = “mypassword” set from = “myemail@hotmail.com” set realname = “Fulcrum” set ssl_force_tls = yes set ssl_starttls = yes set folder = imaps://imap-mail.outlook.com:993 set spoolfile = imaps://imap-mail.outlook.com/INBOX set header_cache=~/.mutt/cache/headers set message_cachedir=~/.mutt/cache/bodies set certificate_file=~/.mutt/certificates set move = no I tried using a gmail account; didnt work. I hope someone here could help me. Regards, Fulcrum
On Thu, 25 Feb 2016 11:18:03 +0800, Fulcrum wrote:
Also, the mutt package availabe in official arch repo has no debugging support so I couldn't figure out what was going wrong.
Hi, I doubt that you need a debug package to solve your issue with mutt, but assumed one day you should need one, this is how it's done for Arch Linux: Install ABS, https://wiki.archlinux.org/index.php/Arch_Build_System#How_to_use_ABS , create the tree, in /var/abs/extra/mutt/ there is the PKGBUILD you need to edit, as described by https://wiki.archlinux.org/index.php/Debug_-_Getting_Traces#General . Regards, Ralf
On 02/25/2016 11:42 AM, Ralf Mardorf wrote:
I doubt that you need a debug package to solve your issue with mutt,
Thanks Ralf, Actually I'm not an advanced user. Most of the software that I use generate plentiful logs so whenever there is some problem I can mostly find the cause of my problem buried somewhere in the logs.
but assumed one day you should need one, this is how it's done for Arch Linux:
I did not know that. Thanks!
On Thu, Feb 25, 2016 at 12:29:55PM +0800, Fulcrum wrote:
On 02/25/2016 11:42 AM, Ralf Mardorf wrote:
I doubt that you need a debug package to solve your issue with mutt,
Thanks Ralf,
Actually I'm not an advanced user. Most of the software that I use generate plentiful logs so whenever there is some problem I can mostly find the cause of my problem buried somewhere in the logs.
but assumed one day you should need one, this is how it's done for Arch Linux:
I did not know that. Thanks!
Hello Fulcrum, Feel free to checkout my .muttrc for gmail: https://paste.archlinux.de/Wbz/ if you want crypto and HTML view just reply and I will upload them also. cheers, Chris
On Thu, 2016-02-25 at 11:18 +0800, Fulcrum wrote:
I tried using a gmail account; didnt work. I hope someone here could help me.
I'm not a mutt expert and definitely not a Hotmail expert (sorry!), but I haven't had much trouble connecting to gmail with mutt. Even a mutt invocation as simple as $ mutt -F /dev/null -f imaps://imap.gmail.com/ connects successfully to my gmail account. As a shot in the dark: have you enabled IMAP in your gmail settings[1]? -austin -- 1: https://support.google.com/mail/troubleshooter/1668960
On 02/25/2016 11:53 AM, Austin Adams wrote:
connects successfully to my gmail account. As a shot in the dark: have you enabled IMAP in your gmail settings[1]?
-austin -- 1: https://support.google.com/mail/troubleshooter/1668960
Thanks for the input. I checked my gmail settings. IMAP was indeed disabled. I was able to use thunderbird so I never bothered to check IMAP settings at gmail. Nonetheless, I enabled IMAP access. Still can't connect. On the plus side, I just realized that when mutt tries to authenticate, it tries 'digest-md5' ,'cram-md5', and 'login' methods but never tries 'gssapi'. May be there is something wrong with gssapi related packages on my PC. Regards, Fulcrum
Did you try set smtp_url = smtp://fulcrummike@hotmail.com@smtp-mail.outlook.com:587 and removing the imap authenticators? On 25.02.2016 04:18, Fulcrum wrote:
Hi
I have been trying for hours but cant get mutt working. I used configuration from different forums. They all made sense but neither work. Also, the mutt package availabe in official arch repo has no debugging support so I couldn't figure out what was going wrong. After some internet research and keen eyes on mutt's on-screen logs, I found that mutt was trying to authenticate plainly. Then I learnt about authenticators. I enabled these authenticators:
set imap_authenticators=”digest-md5:gssapi:cram-md5:login” set smtp_authenticators=”digest-md5:gssapi:cram-md5:login”
And now I am exhausted and , quite frankly, frustrated.
The only logs generated by journalctl are:
Feb 25 10:44:15 ARCH mutt[31322]: GSSAPI client step 1 Feb 25 10:44:37 ARCH mutt[31322]: DIGEST-MD5 common mech free Feb 25 10:45:04 ARCH mutt[31328]: GSSAPI client step 1 Feb 25 10:45:06 ARCH mutt[31328]: DIGEST-MD5 common mech free Feb 25 10:45:10 ARCH mutt[31329]: GSSAPI client step 1 Feb 25 10:45:12 ARCH mutt[31329]: DIGEST-MD5 common mech free Feb 25 10:45:40 ARCH mutt[31332]: DIGEST-MD5 common mech free Feb 25 10:48:29 ARCH mutt[31404]: DIGEST-MD5 common mech free Feb 25 10:48:45 ARCH mutt[31406]: GSSAPI client step 1 Feb 25 10:49:18 ARCH mutt[31406]: DIGEST-MD5 common mech free Feb 25 10:50:18 ARCH mutt[31421]: DIGEST-MD5 common mech free Feb 25 10:53:46 ARCH mutt[31530]: GSSAPI client step 1 Feb 25 10:53:49 ARCH mutt[31530]: DIGEST-MD5 common mech free
FYI I have 'cyrus-sasl' and 'cyrus-sasl-gssapi' packages installed. My .muttrc:
set imap_authenticators=”gssapi:digest-md5:cram-md5:login” set smtp_authenticators=”gssapi:digest-md5:cram-md5:login” set imap_user = “myemail@hotmail.com” set imap_pass = “mypassword" set smtp_url = smtp://smtp-mail.outlook.com:465 // Earlier, I tried port 587 set smtp_pass = “mypassword” set from = “myemail@hotmail.com” set realname = “Fulcrum” set ssl_force_tls = yes set ssl_starttls = yes set folder = imaps://imap-mail.outlook.com:993 set spoolfile = imaps://imap-mail.outlook.com/INBOX set header_cache=~/.mutt/cache/headers set message_cachedir=~/.mutt/cache/bodies set certificate_file=~/.mutt/certificates set move = no
I tried using a gmail account; didnt work. I hope someone here could help me.
Regards, Fulcrum
Hi On 02/25/2016 11:34 PM, goa wrote:
Did you try set smtp_url =smtp://fulcrummike@hotmail.com@smtp-mail.outlook.com:587 and removing the imap authenticators?
It didn't work. Mutt tried connecting to imap server, but failed. If I remove the imap authenticators, mutt tries to connect to imap-mail.hotmail.com and the final error is "Login Failed". If I include the imap authenticators, the error is "No authenticators available." Regards,
On jue, 2016-02-25 at 11:18 +0800, Fulcrum wrote:
You don't need this:
set imap_authenticators=”gssapi:digest-md5:cram-md5:login” set smtp_authenticators=”gssapi:digest-md5:cram-md5:login”
You should always use SSL and TLS to connect to an email providerm by the way. If it doesn't support SSL/TLS, well you should run away faster from it than from the black plague and taxmen. Outlook.com supports SSL for IMAP and TLS for SMTP on the receive port (567). And that brings me to point out: When you use a trustworthy SSL or TLS connection, you don't need password authentication thingamagicks. You use PLAIN auth. Outlook.com (and Gmail, Yahoo!, GMX and others) only support PLAIN auth over SSL or TLS.
I tried using a gmail account; didnt work. I hope someone here could help me.
A Gmail account will require OAUTH2 support in the client by default, ---the reason why you can connect with thunderbird, and using POP3 of all things (yuck!) as you pointed out later in this thread that IMAP support was disabled---. You can enable password authentication in the security section at https://myaccount.google.com/ not before being admonished that doing so will probably rob your youth, hair and fortune. On how go about finding out the right parameters to configure mutt with your Outlook.com account (bear with me, hotmail.com is dead and your address is just an alias to an Outlook.com inbox), configure the account in thunderbird as an IMAP account and the review the configuration generated for the account. SMTP settings are at the end of the account settings list in thunderbird.
Regards, Fulcrum
-- Pedro A. López-Valencia http://about.me/palopezv Recession is when your neighbor loses his job. Depression is when you lose yours. -Ronald Reagan
On jue, 2016-02-25 at 14:25 -0500, P. A. López-Valencia wrote:
Outlook.com supports SSL for IMAP and TLS for SMTP on the receive port (567).
Make that port 587. -- Pedro A. López-Valencia http://about.me/palopezv Recession is when your neighbor loses his job. Depression is when you lose yours. -Ronald Reagan
[SOLVED] Hi everybody, On 02/26/2016 03:25 AM, P. A. López-Valencia wrote:
You don't need this:
set imap_authenticators=”gssapi:digest-md5:cram-md5:login” set smtp_authenticators=”gssapi:digest-md5:cram-md5:login”
You were right; I didn't need this. Without these entries I was getting "Login Failed" error. That's why I put these lines in my config file. After I removed these entries, I tried to connect but again failed with a "Login Failed" error. I checked journalctl and it showed that mutt was still trying to use DIGEST-MD5 authenticator (don't know why!). So I put in my .muttrc this line: set imap_authenticators="plain" and it worked. I haven't tested smpt yet but I hope it will work now too.
Outlook.com supports SSL for IMAP and TLS for SMTP on the receive port (567). And that brings me to point out: When you use a trustworthy SSL or TLS connection, you don't need password authentication thingamagicks. You use PLAIN auth. Outlook.com (and Gmail, Yahoo!, GMX and others) only support PLAIN auth over SSL or TLS.
Didn't know that. I read something like this about PLAIN authentication in some forum post but it wasn't explained quite clearly. Thanks guys for your help. Regards,
participants (6)
-
Austin Adams
-
Christian Rebischke
-
Fulcrum
-
goa
-
P. A. López-Valencia
-
Ralf Mardorf