similar to: When will passdb callback to mechanism yield PASSDB_RESULT_NEXT?

Hello, attached is an hg export on top of the current dovecot-2.2 branch, which adds support for a SCRAM-SHA-1 password scheme. Ideally I'd want doveadm pw's rounds flag to apply to this, but that's currently specific to the crypt password scheme, so I left it out for now. Regards, Florian Zeitz -------------- next part -------------- # HG changeset patch # User Florian Zeitz

On Tue, Jun 23, 2020 at 5:17 PM Aki Tuomi <aki.tuomi at open-xchange.com> wrote: > > > On 23/06/2020 12:15 Joe Wong <joewong99 at gmail.com> wrote: > > > > > > Hello, I have added 'y' as nodelay in my passdb query and I see the > following in log: > > > > dovecot: imap-login: Debug: Ignoring unknown passdb extra field: nodelay >

Does anyone know what might cause this? # dovecot --version 1.1.7 Feb 17 18:21:51 imap-proxy-temp dovecot: Panic: auth(default): file passdb-cache.c: line 121 (passdb_cache_lookup_credentials): assertion failed: (*scheme_r != NULL || *password_r == NULL) Feb 17 18:21:51 imap-proxy-temp dovecot: auth(default): Raw backtrace: dovecot-auth [0x42c0ea] -> dovecot-auth [0x42c143] -> dovecot-auth

Hi Everyone, I'm running an IPA server on CentOS 7 successfully and now I want to change my Dovecot setup to use GSSAPI for IMAP authentication instead of a flat "userdb" file. I've already joined the Dovecot box to the IPA domain - ssh and ipa policies and all that are working properly. I read a number of articles on how to configure Dovecot for GSSAPI auth and they all said

Hello Dovecot list, We've been running a really old CentOS 5 server with the stock dovecot from yum (1.0.7) for years and years with absolutely no problems. If it ain't broke, don't fix it, or something like that. Well it finally broke, but only due to the server no longer being able to handle the load of the increasing user base (many thousands now, with hundreds of concurrent

27.10.2016 16:39, Arkadiusz Mi?kiewicz wrote: > On Thursday 27 of October 2016, Timo Sirainen wrote: >> http://dovecot.org/releases/2.2/dovecot-2.2.26.tar.gz >> http://dovecot.org/releases/2.2/dovecot-2.2.26.tar.gz.sig > Please merge to 2.2 branch this fix. I'm hitting that problem on 2.2.25: > > From 6c969ac21a43cc10ee1f1a91a4f39e4864c886cb Mon Sep 17 00:00:00 2001

On 26/09/2018 08:34, Aki Tuomi wrote: > # before current passbd > passdb { > driver = passwd-file > args = username_format=%Lu /etc/dovecot/aliases > } > > # into /etc/dovecot/aliases > alias at user:::::::user=real_username noauthenticate > > This hopefully works. > > Aki This does appear to work, thanks! As an optimization of the alias

Hi, Our organization is currently using a passwd-file user database for our Dovecot installs. However, we now want to provide simple username aliases. We currently use usernames that are -not- equal to the email address, but due to the fact that many major email clients/providers do not even allow you to specifiy a username, we now want to provide aliases where the username is equal to the

Afternoon all. I'm seeing a segfault in dovecot 2.2.12 (debian package 1:2.2.12-2). I can log into dovecot fine with mutt, but the segfaults seem to occur when postfix (2.11.0, debian package 2.11.0-1+b1) tries to deliver a message. This was working fine under 2.2.9 (I can downgrade to that and delivery works). Can anyone help? Doveconf -n, and backtrace follow.

Hi there, Other auth modules (eg passwd-file) allow a username_format to be specified, but not the PAM module. The use-case, is where I want a static userdb configuration which takes the domain into account but still want to use PAM for authentication, eg: userdb { driver = static args = uid=8 gid=12 home=/mnt/storage/mail/vhosts/%d/%n } passdb { driver = pam args = username_format=%n

On Friday 28 of October 2016, Aki Tuomi wrote: > 27.10.2016 16:39, Arkadiusz Mi?kiewicz wrote: > > On Thursday 27 of October 2016, Timo Sirainen wrote: > >> http://dovecot.org/releases/2.2/dovecot-2.2.26.tar.gz > >> http://dovecot.org/releases/2.2/dovecot-2.2.26.tar.gz.sig > > > > Please merge to 2.2 branch this fix. I'm hitting that problem on 2.2.25:

Help, new to dovecot... I want to get some output from my test sessions to confirm that SSL pop and imap are working. How does one get debug output from dovecot? How does one see that dovecot is using SSL in a transaction? I configured dovecot 0.99.13 with: CC=gcc CPPFLAGS=-I/opt/openssl/include LDFLAGS=-L/opt/openssl/lib \ ./configure --prefix=/opt/dovecot --with-ssl=openssl \

does not work :-/ Sep 05 13:49:41 auth: Debug: auth client connected (pid=31115) Sep 05 13:49:41 auth: Debug: client in: AUTH 1 PLAIN service=imap secured session=IFCT0m9Y0KjAqAFk lip=192.168.1.100 rip=192.168.1.100 lport=143 rport=43216 resp=AHBvbGhhbGxlbkBmdWNrYXJvdW5kLm9yZwBQYW5kb3JhMjAwMA== (previous base64 data may contain sensitive data) Sep 05

On Wed, Sep 26, 2018 at 09:34:07AM +0300, Aki Tuomi <aki.tuomi at open-xchange.com> wrote: > # before current passbd > passdb { > ? driver = passwd-file > ? args = username_format=%Lu /etc/dovecot/aliases > } > > # into /etc/dovecot/aliases > alias at user:::::::user=real_username noauthenticate > > This hopefully works. This seems to work fine and I had the

I pasted that block at the end of dovecot.conf, restarted, and got the following in syslog: Oct 22 08:24:32 tgvprod dovecot[7290]: doveconf: Fatal: Error in configuration file /etc/dovecot/dovecot.conf line 106: Expecting '{' Oct 22 08:24:32 tgvprod systemd[1]: dovecot.service: Main process exited, code=exited, status=89/n/a Oct 22 08:24:32 tgvprod systemd[1]: dovecot.service: Failed

Hello, thanks for your reply I already tried with: username_format=%n or auth_username_format=%n but I've same problem Pol > passdb { > driver = pam > args = username_format=%n > } > > also you probably want to consider using driver=passwd instead, if you > really don't need pam due to some special plugins. > > Aki -- Pol

Do I modify auth-system.conf.ext only (sorry for the question) if yes, I've same problem Pol On 2017-09-05 13:34, Aki Tuomi wrote: > Try configuring like this: > > passdb { > args = scheme=SHA256 username_format=%u /etc/dovecot/users > driver = passwd-file > } > > passdb { > driver = static > args = username=%n noauthenticate > skip = authenticated

Setting passdb to passwd and enabling cram-md5 or digest-md5 makes dovecot crash. The documentation says that I can use md5 with passwd. I had to use strace to figure it, because dovecot segfaults and doesn't log the error. Using CenOS 5.2 x86_64 Regards, Miguel # dovecot -n # 1.1.2: /etc/dovecot.conf listen: 127.0.0.1 login_dir: /var/run/dovecot/login login_executable(default):

Sure :) thanks cat /var/log/dovecot/[...] Sep 05 13:26:02 auth: Debug: auth client connected (pid=30131) Sep 05 13:26:02 auth: Debug: client in: AUTH 1 PLAIN service=imap secured session=JK0Bfm9YuqfAqAFk lip=192.168.1.100 rip=192.168.1.100 lport=143 rport=42938 resp=AG1heEBmdWNrYXJvdW5kLm9yZwBQYW5kb3JhMjAwMA== (previous base64 data may contain

A little problem, which is bugging me: when using PAM authentication, Dovecot (0.99.5) does not set the PAM_RHOST item, so the PAM modules cannot know who the client is. We need this for some PAM module doing access control. Changing passdb-pam.c to pam_set_item it seems trivial, but I'm bugged as to how to get the client name from there. It seems not to be available in the auth_request