similar to: Possible bug with proxy in 2.0.4

Hello, i'm test system dovecot (proxy with director) and backend storage, auth LDAP server (user plain passwords) If i use plain auth, work fine. If connect DIGEST-MD5 or CRAM-MD5 proxy not redirect connection (Requested DIGEST-MD5 scheme, but we have a NULL password) ### Frontend proxy+director # dovecot -n # 2.2.19: /usr/local/etc/dovecot/dovecot.conf # OS: FreeBSD 10.2-RELEASE amd64

Hello, I'm using proxy_maybe and auth_default_realm. It seems that when a user logs in without the domain name, relying on auth_default_realm, and the "host" field points to the local server, I get the Proxying loops to itself error. It does work as expected - log on to the local server without proxying, if the user does include the domain name in the login. (IP's and

Aki, thanks, I fixed typo but error persists: Mar 7 10:55:54 mail dovecot: auth: Debug: auth client connected (pid=10828) Mar 7 10:55:55 mail dovecot: auth: Debug: client in: AUTH#0111#011CRAM-MD5#011service=imap#011secured#011session=FIH/6tJm4gDAqHoB#011lip=192.168.122.202#011rip=192.168.122.1#011lport=993#011rport=37090 Mar 7 10:55:55 mail dovecot: auth: Debug: client passdb out:

Dear All, Is there any easy way to upgrade Dovecot like yum command? Or I have to delete the current and install the new version then change the setting?> I will appreciate if you can tell me the steps please? Best Regards Arif --- On Fri, 1/10/10, dovecot-request at dovecot.org <dovecot-request at dovecot.org> wrote: From: dovecot-request at dovecot.org <dovecot-request at

I'm running dovecot with vpopmail. Here's the configuration: [root at wong log]# dovecot -n # 2.0.11: /etc/dovecot/dovecot.conf # OS: Linux 2.6.18-238.9.1.el5 i686 CentOS release 5.6 (Final) auth_cache_size = 32 M auth_mechanisms = plain login digest-md5 cram-md5 auth_username_format = %Lu first_valid_uid = 89 log_path = /var/log/dovecot.log login_greeting = Dovecot toaster ready.

Hi! Who can tell me why I have double login lines for some accounts? Oct 31 12:35:36 imap-login: Info: Login: user=<anmeyer at anup.de>, method=CRAM-MD5, rip=84.179.59.177, lip=78.47.3.18, mpid=29905, TLS, TLSv1 with cipher RC4-MD5 (128/128 bits) Oct 31 12:35:36 imap-login: Info: Login: user=<anmeyer at anup.de>, method=CRAM-MD5, rip=84.179.59.177, lip=78.47.3.18, mpid=29906, TLS,

Hi login_log_format_elements = user=<%u> method=%m rip=%r %k is it possible to get rid of the "proxy(test at testserver.rhsoft.net): started proxying to 127.0.0.1:143: " part because on a proxy-only server i know that and it is explicitly not listed in "login_log_format_elements" as well as for the "TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA" it would be

Hi Timo, As http://wiki2.dovecot.org/Authentication/MasterUsers states, currently the first way for master users to log in as other users only supports PLAIN SASL mechanism, and because DIGEST-MD5 uses user name to calculate MD5 digest, the second way can't support DIGEST-MD5. I enhance the code to support DIGEST-MD5 too for the first way, please review the attached patch against

Hi, I get this error even when user logins succesfully: Mar 7 10:41:16 mail dovecot: auth: Debug: client in: AUTH#0111#011CRAM-MD5#011service=imap#011secured#011session=maOgttJmCADAqHoB#011lip=192.168.122.202#011rip=192.168.122.1#011lport=993#011rport=36872 Mar 7 10:41:16 mail dovecot: auth: Debug: client passdb out: CONT#0111#011PDYyMjM4NTMwODIyODI0MDguMTUyMDQzMDA3NkBtYWlsLmV4YW1wbGUuY29tPg==

Hi, I want to use CRAM-MD5 or DIGEST-MD5 (non-plaintext) authentication for master users, but Dovecot 2.2.13 rejects it with the following log: Sep 1 06:18:08 localhost dovecot: auth: passwd-file(masteruser,10.0.1.20,master,<ZA1s9/oBgAAKAAEU>): Master user logging in as u0001 Sep 1 06:18:08 localhost dovecot: auth: cram-md5(u0001 at example.jp,10.0.1.20,<ZA1s9/oBgAAKAAEU>):

Hello, the attached patch for Dovecot 2.2.4 improves the logging to include information about the cipher suite used for a TLS connection. Here is an example log line: Aug 13 21:49:55 colwyn dovecot: imap-login: Login: user=<tron>, method=CRAM-MD5, rip=2001:8b0:114:1::2, lip=2001:8b0:114:1::2, mpid=10567, TLS=<TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)>,

Hello list, I am currently testing a setup for a PoC wit this configuration. - 1 x Frontend dovecot for proxying IMAP/POP3/LMTP/ManageSieve/Submission - 2 x Backend dovecot with local mail storage The frontend does the user authentification and communicate with the backends using a master password The fronted accepts PLAIN and LOGIN auth mechanisms and talk with backends using PLAIN auth

Hello! Aki Tuomi <aki.tuomi at open-xchange.com> schrieb am 20.03.20 um 16:06:48 Uhr: > > On 20/03/2020 15:55 ratatouille <ratatouille at bitclusive.de> wrote: > > > > > > Hello! > > > > I have one systemuser on my testsystem running CentOS. All other users live in a mysql- database. > > > > I created a /etc/dovecot/users file and

Hello! Setup again to authenticate my users with MySQL but can't login. Sep 13 11:55:49 auth: Info: passwd-file(a.meyer at nimmini.de,95.88.63.177,<R7Qe9J0fTgBfWD+x>): unknown user Sep 13 11:55:49 auth: Info: passwd-file(a.meyer at nimmini.de,95.88.63.177,<R7Qe9J0fTgBfWD+x>): unknown user Sep 13 11:55:49 imap-login: Info: Login: user=<a.meyer at nimmini.de>,

Dear All, Thanks for all your replied but still I don't know how to install from 1.0.7 to 1.2.14. What should I consider to keep the same configuration during or after upgrade? It is the first time I am trying to upgrade my Dovecot. Thank a lot for your help --- On Fri, 1/10/10, dovecot-request at dovecot.org <dovecot-request at dovecot.org> wrote: From: dovecot-request at

My bad. Userdb does not support scheme keyvalue, just remove it. Aki > On 07 March 2018 at 15:57 Sergio Belkin <sebelk at gmail.com> wrote: > > > Aki, > > thanks, I fixed typo but error persists: > Mar 7 10:55:54 mail dovecot: auth: Debug: auth client connected (pid=10828) > Mar 7 10:55:55 mail dovecot: auth: Debug: client in: >

for nomal operations * login_log_format_elements = %r %m %k * login_log_format = %$: %s would be perfect because "proxy(h.reindl at thelounge.net)" contains the username *but* in case of auth errors "Disconnected (auth failed, 1 attempts in 2 secs)" does not show the username - hence currently there exists no way to avoid username double-logging in normal

Hi. Is it possible to use GSSAPI authentication and deny passdb together? Seems it doesn't work as I expect: GSSAPI doesn't check deny passdb, so I'm not able to restrict access to GSSAPI-users. I can see these in logs when user tries to connect with PLAIN authentication (via pam_krb5): Oct 4 11:14:31 vm03 auth: Debug: passwd-file(testuser,172.17.0.123): lookup: user=testuser

Hello, i have a setup with two director servers pointing to two backends. I don't care that much for load balancing, my main goal is high availability. CRAM-MD5 auth is working fine if I connect directly to the backends, but the director only supports AUTH=PLAIN because of the static passdb. director config: > passdb { > driver = static > args = nopassword=y proxy=y > } >

OK. "passdb/userdb" Setting part $ dovecot -n (Excerpt from change) ---------------------------------------------------------------------------- --------------------- passdb { args = scheme=CRYPT username_format=%u /etc/dovecot/users.auth driver = passwd-file } userdb { args = username_format=%u /etc/dovecot/users.auth driver = passwd-file } protocol lmtp { info_log_path =