search for: auth_debug_passwords

>From the configuration notes (1.0.10), it sounds like setting 'auth_debug_passwords' will only log the user supplied password if there was a mismatch.. When I set it (with auth_debug=no), I get a good amount of auth debug info, regardless of password matching.. ------ dovecot.conf: # In case of password mismatches, log the passwords and used scheme so the # problem can be deb...

Hi. I'm new to Dovecot and about to start using it in production. In the config file, I set the option, auth_debug_passwords, to yes. I do not see any failed passwords logged, however. It did cause more verbose authentication logging, but failed passwords are still hidden. I have also set these options to yes, because I thought they might be required for auth_debug_passwords to work: auth_verbose = yes auth_debug = y...

Has anyone tried patching the 1.2.x source to force logging of all passwords submitted during authentication, not just those that fail?

...se give me a sample 10-auth.conf for NTML and any other supporting settings or configs I need? My current/working dovecot settings, which have been running perfectly for well over a year now, are: $ dovecot -n # 2.2.15: /usr/local/etc/dovecot/dovecot.conf # OS: Linux 3.10.17 x86_64 Slackware 14.1 auth_debug_passwords = yes auth_mechanisms = plain login auth_verbose = yes auth_verbose_passwords = plain disable_plaintext_auth = no info_log_path = /var/log/dovecot_info mail_location = maildir:~/Maildir passdb { driver = shadow } protocols = imap ssl_cert = </etc/ssl/certs/OHPRS/GoDaddy/Apache/2015-08-14/57aa6...

Hello Timo, I just launched rc1 with auth_verbose = yes auth_debug = yes #auth_debug_passwords = no and on a wrong password, I see my crypted passwd in the log : userPassword(password)={Crypt}xxxxxxxx Is that normal, since I assume that auth_debug_passwords defaults to no ? -- Thomas Hummel | Institut Pasteur <hummel at pasteur.fr> | P?le informatique - syst?mes et r?seau

...configs I need? > > > > My current/working dovecot settings, which have been running perfectly for well over a year > > now, are: > > > > $ dovecot -n > > # 2.2.15: /usr/local/etc/dovecot/dovecot.conf > > # OS: Linux 3.10.17 x86_64 Slackware 14.1 > > auth_debug_passwords = yes > > auth_mechanisms = plain login > > auth_verbose = yes > > auth_verbose_passwords = plain > > disable_plaintext_auth = no > > info_log_path = /var/log/dovecot_info > > mail_location = maildir:~/Maildir > > passdb { > > driver = shadow > &...

...configs I need? > > > > My current/working dovecot settings, which have been running perfectly for well over a year > > now, are: > > > > $ dovecot -n > > # 2.2.15: /usr/local/etc/dovecot/dovecot.conf > > # OS: Linux 3.10.17 x86_64 Slackware 14.1 > > auth_debug_passwords = yes > > auth_mechanisms = plain login > > auth_verbose = yes > > auth_verbose_passwords = plain > > disable_plaintext_auth = no > > info_log_path = /var/log/dovecot_info > > mail_location = maildir:~/Maildir > > passdb { > > driver = shadow > &...

...nto the Windows AD workstations and their Outlook clients. If anyone has actually done this I'd appreciate some tips. My various attempts have not been successful. Here is my current config: $ doveconf -n # 2.2.15: /usr/local/etc/dovecot/dovecot.conf # OS: Linux 3.10.17 x86_64 Slackware 14.1 auth_debug_passwords = yes auth_mechanisms = plain login auth_verbose = yes auth_verbose_passwords = plain disable_plaintext_auth = no info_log_path = /var/log/dovecot_info mail_location = maildir:~/Maildir passdb { driver = shadow } protocols = imap ssl_cert = </etc/ssl/certs/OHPRS/GoDaddy/Apache/c5fe0cc8242d6030...

...: auth: Fatal: Unknown database driver 'mysql' dovecot: master: Error: service(auth): command startup failed, throttling But a first thing would be to log the real errors, if there are any, so I set in /etc/dovecot/conf.d/10-logging.conf auth_verbose, auth_verbose_passwords, auth_debug, auth_debug_passwords, mail_debug, verbose_ssl all to yes and I set: debug_log_path = /var/log/dovecot-debug.log but there is no logfile after restarting dovecot. How can I enable a (verbous) own Logfile in Dovecot? frank

I have added "auth_debug_password=yes" to "10-logging.conf" and restarted dovecot.?But I do not see any information about the password in the logs. Does this mean that the thunderbird does not send the password??Although it asks for the password and I enter one. New log: dovecot: master: Warning: Killed with signal 15 (by pid=19769 uid=0 code=kill) dovecot: master: Dovecot

...rnet is how to configure address books using > LDAP. > > 2. Should I remove "passdb { drive = shadow } from the dovecot > configuration? > > Anybody? > > $ doveconf -n > # 2.2.15: /usr/local/etc/dovecot/dovecot.conf > # OS: Linux 3.10.17 x86_64 Slackware 14.1 > auth_debug_passwords = yes > auth_mechanisms = plain login > auth_verbose = yes > auth_verbose_passwords = plain > disable_plaintext_auth = no > info_log_path = /var/log/dovecot_info > mail_location = maildir:~/Maildir > passdb { > driver = shadow > } > passdb { > args = /etc/dovecot/do...

...ook client to Dovecot on a Samba4 AD/DC should be a very common implementation. Has someone done this successfully? Immediately below is my doveconf -n and below that the dovecot log messages. > doveconf -n # 2.2.15: /usr/local/etc/dovecot/dovecot.conf # OS: Linux 3.10.17 x86_64 Slackware 14.1 auth_debug_passwords = yes auth_mechanisms = plain ntlm login auth_use_winbind = yes auth_verbose = yes auth_verbose_passwords = plain disable_plaintext_auth = no info_log_path = /var/log/dovecot_info mail_location = maildir:~/Maildir passdb { driver = shadow } protocols = imap ssl_cert = </etc/ssl/certs/OHPRS/GoD...

...a setup with system users, i would prefer to use dovecots sasl implementation. dovecot --version = 2.1.7 cat dovecot.conf ###################### ###################### disable_plaintext_auth = no mail_privileged_group = mail log_path = /var/log/dovecot.log # auth_verbose=yes # auth_debug=yes # auth_debug_passwords=yes mail_debug=yes # verbose_ssl=yes passdb { args = /etc/dovecot/dovecot-sql.conf driver = sql } userdb { driver = prefetch } userdb { args = /etc/dovecot/dovecot-sql.conf driver = sql } protocols = "pop3 imap lmtp" protocol imap { mail_plugins = " autocreate" }...

...ook client to Dovecot on a Samba4 AD/DC should be a very common implementation. Has someone done this successfully? Immediately below is my doveconf -n and below that the dovecot log messages. > doveconf -n # 2.2.15: /usr/local/etc/dovecot/dovecot.conf # OS: Linux 3.10.17 x86_64 Slackware 14.1 auth_debug_passwords = yes auth_mechanisms = plain ntlm login auth_use_winbind = yes auth_verbose = yes auth_verbose_passwords = plain disable_plaintext_auth = no info_log_path = /var/log/dovecot_info mail_location = maildir:~/Maildir passdb { driver = shadow } protocols = imap ssl_cert = </etc/ssl/certs/OHPRS/GoD...

...doesn't work. All I can seem to find on the Internet is how to configure address books using LDAP. 2. Should I remove "passdb { drive = shadow } from the dovecot configuration? Anybody? $ doveconf -n # 2.2.15: /usr/local/etc/dovecot/dovecot.conf # OS: Linux 3.10.17 x86_64 Slackware 14.1 auth_debug_passwords = yes auth_mechanisms = plain login auth_verbose = yes auth_verbose_passwords = plain disable_plaintext_auth = no info_log_path = /var/log/dovecot_info mail_location = maildir:~/Maildir passdb { driver = shadow } passdb { args = /etc/dovecot/dovecot-ldap.conf.ext driver = ldap } protocols = i...

...be > a very common implementation. Has someone done this successfully? > > Immediately below is my doveconf -n and below that the dovecot log > messages. > >> doveconf -n > > # 2.2.15: /usr/local/etc/dovecot/dovecot.conf > # OS: Linux 3.10.17 x86_64 Slackware 14.1 > auth_debug_passwords = yes > auth_mechanisms = plain ntlm login > auth_use_winbind = yes > auth_verbose = yes > auth_verbose_passwords = plain > disable_plaintext_auth = no > info_log_path = /var/log/dovecot_info > mail_location = maildir:~/Maildir > passdb { > driver = shadow > } > pro...

...hing on the literal string, e.g. "%{userdb:real_username}" ). And I'm not even sure if director_username_hash has access to any passdb/userdb data. Is there a debug setting that would show what string director is using to do the hashing? Current debug settings are: auth_debug = yes auth_debug_passwords = yes mail_debug = yes but not a peep as to the string that director is hashing on. -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://dovecot.org/pipermail/dovecot/attachments/20190412/14267f32/attachment.html>

Hi, I'm working on a setup of dovecot 2 + netqmail + vpopmail 5.5 but auth doesn't works :( dovecot -n # 2.0.1: /etc/dovecot/dovecot/dovecot.conf # OS: Linux 2.6.35.1-rscloud x86_64 Ubuntu 10.04.1 LTS auth_debug = yes auth_debug_passwords = yes auth_mechanisms = plain login cram-md5 auth_verbose = yes auth_verbose_passwords = plain disable_plaintext_auth = no log_path = /var/log/dovecot/dovecot.log login_greeting = Dovecot ready. mail_debug = yes passdb { driver = vpopmail } ssl_cert = </etc/ssl/certs/dovecot.pem ssl_key = &lt...

...eone done this successfully? > > > > Immediately below is my doveconf -n and below that the dovecot log > > messages. > > > >> doveconf -n > > > > # 2.2.15: /usr/local/etc/dovecot/dovecot.conf > > # OS: Linux 3.10.17 x86_64 Slackware 14.1 > > auth_debug_passwords = yes > > auth_mechanisms = plain ntlm login > > auth_use_winbind = yes > > auth_verbose = yes > > auth_verbose_passwords = plain > > disable_plaintext_auth = no > > info_log_path = /var/log/dovecot_info > > mail_location = maildir:~/Maildir > > passd...

I have turned on 'auth_debug_passwords=yes? in dovecot.conf. I?m trying to get Fail2ban to detect this log line: Sep 11 15:52:49 mail dovecot[54239]: auth-worker(10094): sql(user at bordo.com.au <mailto:user at bordo.com.au>,::1,<L2xqieNYeM4AAAAAAAAAAAAAAAAAAAAB>): Password mismatch (given password: 2) I?ve added it as th...