search for: imap_authenticators

hi i have a strange problem with my dovecot installtion: i configured it to accept digest-md5 authentication only but for some reason mailclients (i tried mutt and thunderbird so far) want to log with PLAIN (which fails of course). authentication basically works, e.g. if i explicitly set set imap_authenticators="digest-md5 in .muttrc everything works... any idea what is going wrong? config attached below tia yours albert # /etc/dovecot/dovecot.conf log_timestamp: %Y-%m-%d %H:%M:%S protocols: imaps pop3s ssl_listen(default): *:22993 ssl_listen(imap): *:22993 ssl_listen(pop3): *:22995 ssl_cipher_...

Good morning all, I''ve been using the imap_authenticatable plugin for about a year now without incident. All of a sudden, I tried logging in this morning and this error is showing up in the logs. Does anyone have any idea what could be causing this or how to fix it? Thanks, Pete NoMethodError (undefined method `disconnect'' for nil:NilClass):

Dear all, I use Dovecot SASL (2.1.15) on Ubuntu 12.04 for IMAP authentication and Postfix SASL authentication. I tried to setup SCRAM-SHA-1 as SASL mechanism. This works well on Dovecot's client side towards my OpenLDAP server (with libsasl-2), but fails on the server side (IMAP and SMTP). In the following, there's an extract from Dovecot's log, when using mutt as SMTP client:

...got an no >> auth failure. > Mutt lets me accept, but I get "No authenticators available", and the mutt screen is blank. > When it asked me for a password previously it was because it fell back to PLAIN authentication, > which worked. Now my /etc/Muttrc has > > set imap_authenticators="gssapi" > > to prevent that. > >> Also figure out where dovecot auth debug log entries get written (here >> dovecot writes logs to mail.info, mail.error, mail.log, debug only ends >> up in mail.log). > My /etc/dovecot.conf has > > # debug_log_path = /v...

OK, let me go through exactly what you did: you: > Here's the test (I must run mutt not telnet like i mentioned earlier to > get the imap tickets). > > root at server:~# kinit achim > Password for achim at DOMAIN.LOCAL: > [I enter my password] As root on AD/DC mail.hprs.local: me: $ kinit mark Password for mark at HPRS.LOCAL: [I enter my password] you: >

...d to enter an password or got an no > auth failure. Mutt lets me accept, but I get "No authenticators available", and the mutt screen is blank. When it asked me for a password previously it was because it fell back to PLAIN authentication, which worked. Now my /etc/Muttrc has set imap_authenticators="gssapi" to prevent that. > Also figure out where dovecot auth debug log entries get written (here > dovecot writes logs to mail.info, mail.error, mail.log, debug only ends > up in mail.log). My /etc/dovecot.conf has # debug_log_path = /var/log/Dovecot/dovecot_debug.log c...

...got an no >> auth failure. > Mutt lets me accept, but I get "No authenticators available", and the mutt screen is blank. > When it asked me for a password previously it was because it fell back to PLAIN authentication, > which worked. Now my /etc/Muttrc has > > set imap_authenticators="gssapi" > > to prevent that. > >> Also figure out where dovecot auth debug log entries get written (here >> dovecot writes logs to mail.info, mail.error, mail.log, debug only ends >> up in mail.log). > My /etc/dovecot.conf has > > # debug_log_path = /v...

...nterface showing my imap://mark at mail.ohprs.org/INBOX. Nothing in maillog, but dovecot log show a successful PLAIN authentication. If I configure dovecot for only gssapi and run mutt it again, I get the messge "No authenticators available". I then created /tmp/testMuttrc with: set imap_authenticators="gssapi" and ran MAIL=imap://mark at mail.ohprs.org/ mutt -F /tmp/testMuttrc same: "No authenticators available" It's as if dovecot knows nothing about gssapi, so I did: $ dovecot --build-options Build options: ioloop=epoll notify=inotify ipv6 openssl io_block_size=819...

...k at mail.ohprs.org/INBOX. > > Nothing in maillog, but dovecot log show a successful PLAIN authentication. If I configure > dovecot for only gssapi and run mutt it again, I get the messge "No authenticators available". > > I then created /tmp/testMuttrc with: > > set imap_authenticators="gssapi" > > and ran > > MAIL=imap://mark at mail.ohprs.org/ mutt -F /tmp/testMuttrc > > same: "No authenticators available" > > It's as if dovecot knows nothing about gssapi, so I did: > > $ dovecot --build-options > Build options: ioloop=ep...

...hing in maillog, but dovecot log show a successful PLAIN >> authentication. If I configure >> dovecot for only gssapi and run mutt it again, I get the messge "No >> authenticators available". >> >> I then created /tmp/testMuttrc with: >> >> set imap_authenticators="gssapi" >> >> and ran >> >> MAIL=imap://mark at mail.ohprs.org/ mutt -F /tmp/testMuttrc >> >> same: "No authenticators available" >> >> It's as if dovecot knows nothing about gssapi, so I did: >> >> $ dovecot --bui...

Did a few test here "auth_gssapi_hostname = "$ALL"" is no longer required with dovecot (2.2.13 here). Add "auth_debug=yes" to your dovecor config. 192.168.100.1 is my clients ip 192.168.100.101 is the servers ag is the domain account username I use to login to windows and also the username configured in thunderbird. On my debian system an package named