similar to: auth_debug_passwords only on mismatches?

Hello I am struggling with Dovecot 2 (coming from Dovecot 1.0.10) with mysql Authentification for Postfix. I get errors when using it: dovecot: 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

Hello, i have an ubuntu 8.04 LTS Virtual Server with Dovecot 1.0.10 and postfix. Now i tried to update Dovecot because i need Quota, which is not possible in 1.0 but in 1.2 So i added the packages to my /etc/apt/sources.list: deb http://codex.xiaoka.com/apt hardy main restricted deb http://archive.ubuntu.com/ubuntu hardy-backports main universe multiverse restricted and updated dovecot with

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:

Hello, We're having difficulty with our updated cluster of dovecot servers accessing the email storage on the NFS mounts.? It seems index files get corrupted when 2 backend mailservers access the same account, and from documentation setting up a director proxy in front of the backup servers.? I'm trying to just set up a straight proxy first, which the documents say is the first step, and

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

hi everyone could someone show me there sasl configuration section in their dovecot.conf, i have postfix and dovecot setup for virtual users (no system users) everything works fine including tls, i have tried various examples off the web for sasl but they either have obsolete parameters or are for a setup with system users, i would prefer to use dovecots sasl implementation. dovecot --version =

TL;DR: Can director_username_hash use %{userdb:...} or %{passdb:...} ? ==================================== This is on Ubuntu Precise, running dovecot 2.2.36. It's a fully production, director-ized env, so assume everything is working correctly. Happy to post doveconf if it's relevant but wanted to ask a general question first. I was curious if there's a way to get userdb/passdb

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 =

Hi! I used "auth_debug=yes" and "auth_debug_passwords=yes". But I only see connects and disconnects: Apr 11 09:17:43 dovecot: POP3(info at xxxx.xx): Disconnected: Logged out top=0/0, retr=0/0, del=0/0, size=0 Apr 11 09:17:43 dovecot: POP3(info at xxxx.xx): Disconnected: Logged out top=0/0, retr=0/0, del=0/0, size=0 Apr 11 09:18:11 dovecot: pop3-login: Login:

Hi, We?re migrating to a Cpanel hosting system. Our passwords are currently stored in MD5. I looked at the post login scripting to be able to start storing the plain text passwords as people login temporarily so we can automate our migration. It seems that the password is not available in the post login environment variables. Is there any way we can get access to the plain text password upon

I had Dovecot running very well on Ubuntu 14.04. Then I decided that since That version of Ubuntu was now out of support, I would build a new server on 18.04, which has been done. I thought I could take the old dovecot.conf and everything in conf.d that had been customized and drop it in place, and everything would just work. That has proven not to be correct. The files that had been edited

Hi, We are migrating from a windows server and i have very few stats as to what our current concurrent usage stats are other than about 50,000 active users and 90,000 email messages a day inbound 20,000 outbound. Anyone got some tips for tuning dovecot to handle this load? Below is my config - do the values of login_process_size etc sound correct? Also my logs seem to be written out as root

Hi, Im attempting to configure dovecot for the first time, Im trying to use a MySQL DB that is currently used by tpop3d as Ive read they support the same password format. My main prob currently, apart from that it doesnt work lol, is that Ive enabled the following debugging in dovecot.conf auth_debug = yes auth_debug_passwords = yes auth_verbose = yes But Im getting basically zero info

Hello, Absolutely, thanks, here it is: # 2.2.27 (c0f36b0): /etc/dovecot/dovecot.conf # Pigeonhole version 0.4.16 (fed8554) # OS: Linux 4.9.0-8-amd64 x86_64 Debian 9.6 auth_debug = yes auth_mechanisms = plain login auth_verbose = yes disable_plaintext_auth = no login_greeting = Welcome to easyMail. mail_debug = yes mail_location = mbox:~/mail:INBOX=/var/mail/%u mail_plugins = " mail_log

After upgrading my IMAP server to the new debian stable, and upgrading dovecot from 1.x to 2.1.7 in the process, dovecot no longer logs anything to /var/log/mail.*. The last entries there are from before the upgrade, and no starts or error messages or failed login attempts, since then, have been logged. Does anyone know what might cause this? "doveconf -n" doesn't mention any of

OSX 10.13.6 High Sierra, dovecot 2.3.2.1 dovecot starts up and runs but dies as soon as my mail client makes a request with log and config below. And advice appreciated. Thanks Mike 20180810-083730 auth: Debug: auth client connected (pid=77432) 20180810-083730 auth: Debug: client in: AUTH??? 1??? PLAIN service=imap??? secured??? session=xo1p2BRzZNd/AAAB lip=127.0.0.1??? rip=127.0.0.1???

Hi, everyone, 1. As advised in?Debugging Authentication, I turned on auth_debug and auth_debug_passwords, and now in the mail log I get an additional message: dovecot: auth: passwd(xxx,xxx,<40AjQMFHSLVLGJAC>): invalid password field '*' Of course neither the password I tried nor the actual password was '*'. That's what's in /etc/passwd, but dovecot isn't just

Does anyone have any idea regarding this? On 17 Nov 2017 11:36, "Tomislav Perisic" <tomiperisic at gmail.com> wrote: Hi, We have 2 servers, server A and server B. Server A has: Postfix dovecot-2.2.33.2-1.el6.x86_64 Server B has: dovecot-2.2.33.2-1.el6.x86_64 dovecot-pigeonhole-2.2.33.2-1.el6.x86_64 Server A receives email on postfix, dovecot then takes that email from

Dear dovecot list. I'm setting up my own VPS and working through getting mail to work. Here is my dovecot -n $dovecot -n maildir:%h/%d/%n/mail : layout=fs # 2.1.7: /etc/dovecot/dovecot.conf # OS: Linux 2.6.32-5-xen-amd64 x86_64 Debian 6.0.3 auth_debug = yes auth_debug_passwords = yes auth_mechanisms = plain login cram-md5 auth_verbose = yes auth_verbose_passwords = plain

I've switched a user to being an active directory user. That user's email client authorizes just fine with dovecot using GSSAPI. However, now his iPhone won't authorize. In the dovecot log file I get: Dec 01 14:27:28 auth: Debug: client in: AUTH 1 PLAIN service=imap secured session=q4n3W0xfggBiZj9s lip=98.102.63.107 rip=98.102.63.108 lport=993