similar to: Disable PAM

Yep. Just remove any passdb/userdb pam blocks ---Aki TuomiDovecot oy -------- Original message --------From: Travis Dolan <travis.dolan at gmail.com> Date: 17/10/2017 17:40 (GMT+02:00) To: dovecot at dovecot.org Subject: Disable PAM Can I disable PAM auth if all my username/password lookups are via a database connection? I would love to get rid of the following lines in my logs... Oct

Hi Everyone, I made some small changes in my dovecot setup to switch it from looking up users and passwords from a mix of ldap (i.e. freeipa) and password files. One of the changes was to switch from using one id for all authentication to using individual ids) It's working fine with Evolution. I have one account authenticating with GSSAPI, which is my userid for logging into my desktop and

On Wed, 2020-09-16 at 23:03 -0400, Ranbir wrote: > auth worker: PASSV: pam_sss(dovecot:auth): authentication failure; > logname= uid=97 euid=97 tty=dovecot ruser=ranbir rhost=1.2.3.4 > user=ranbir > auth worker: PASSV: pam_sss(dovecot:auth): received for user ranbir: > 17 (Failure setting user credentials) > It doesn't matter what user or group I use for unix_listener. If I

Sorry, small typo passdb { driver = static args = user=%n noauthenticate } Aki On 05.09.2017 14:51, Pol Hallen wrote: > 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

Hi, I am trying to establish an IMAP mail service accessible using a current Thunderbird on a laptop. I used Macports to install Dovecot2 (2.1.5) on an older Snow Leopard Mac mini with Intel Core Duo (specifically a Macmini1,1). My goal is to be able to run sieve under dovecot2 and offload the email triage from my work laptop to the little mail server. Mail appears to show up on the server

When I open the mail client (thunderbird), I can access the mailboxes and all of a sudden, I am loosing the authenticated session. Any idea's where to look? Jan 17 12:42:04 mail04 dovecot: imap-login: Login: user=<usertest>, method=PLAIN, rip=192.168.10.219, lip=192.168.10.44, mpid=13403, TLS, session=<NsYo4qV/CNfAqArb> Jan 17 12:42:04 mail04 dovecot: imap(usertest): Debug:

Hi, I have been running dovecot successfully on OS X Mavericks for several months. After upgrading to Yosemite, however, PAM authentication for dovecot is failing. Or rather, creating the PAM session is failing. Either way, I can't get to my e-mail. $ /usr/pkg/sbin/dovecot --version 2.2.15 $ /usr/pkg/sbin/dovecot -n # 2.2.15: /usr/pkg/etc/dovecot/dovecot.conf # OS: Darwin 14.0.0 x86_64 hfs

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

Good day Folks, I am trying to setup a mail server based on dovecot(with imap and pop3) and postfix as a smtp on debian jessie/sid. The login its system user. After I have tried to configure the client (Icedove), this last can find the imap, pop3 and smtp servers; but the can't be verified. Please see below my dovecot, postfix configurations and log details. erickom at ajk:/etc/postfix$

Hello all, Following the Dovecot wiki and migration help, we recently migrated our core IMAP systems from Courier to Dovecot on Solaris. So far it's been working great, but I have one issue that I'm curious about. Just as the docs mention, we also use "syslog_facility = mail" for logging. Unlike in the past, failed PAM auth attempts are now getting logged as mail.error: Nov

Hi, I'm fighting all weekend on with auth and pam to authenticate local system users. testuser is such local user and is in passwd and shadow. I want to have local system users (testuser is one of them) and virtual users. The virtual part works fine but I cannot get the local user to connect. Still pam fails finding the user. The suggested password mismatch at the end is, in my eyes,

> On 11 Sep 2017, at 5:10 pm, Christian Kivalo <ml+dovecot at valo.at> wrote: > > On 2017-09-11 08:57, James Brown wrote: >> 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

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 the last line of my dovecot filter regex: failregex =

On 2017-09-11 08:57, James Brown wrote: > 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

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 } passdb { driver = pam skip = authenticated } On 05.09.2017 14:29, Pol Hallen wrote: > Sure :) thanks > > cat /var/log/dovecot/[...] > > Sep 05 13:26:02 auth: Debug:

Getting this: auth-worker(5045): Error: pam(kremels,xxx.xxx.xxx.xxx: pam_authenticate() failed: authentication error (/etc/pam.d/dovecot missing?) # cat /etc/pam.d/dovcot auth required pam_unix.so nullok account required pam_unix.so (file was last updated in April of 2018) passdb { username_filter = "!*@*" driver = pam } userdb { driver = passwd } service auth {

No, you modify dovecot.conf Aki On 05.09.2017 14:40, Pol Hallen wrote: > 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 =

While using Ubuntu 10.10 + Dovecot 1.2.12 + Postfix 2.7.1-1: To enable virtual accounts, I am using the following /etc/dovecot/auth.d/virtualsomename.auth file: passdb passwd-file { args = /etc/dovecot/passwd } userdb static { args = uid=vmail gid=vmail home=/home/vmail/%u } EOT cat /etc/dovecot/passwd looks like this: test:{PLAIN}pass bill:{PLAIN}secret timo at

I setup dovecot on my laptop to practice on. I was following some of the information on this page: https://help.ubuntu.com/community/PostfixVirtualMailBoxClamSmtpHowto#Testing Your Setup I created the in this format: user:{plain}pass:1000:1000::/home/user::userdb_mail=maildir:~/Maildir for userdb passwd-file. I used smart for the user and wade for the password (its just for testing) and then

*** dovecot.conf *** ## Dovecot configuration file # If you're in a hurry, see http://wiki2.dovecot.org/QuickConfiguration # "doveconf -n" command gives a clean output of the changed settings. Use it # instead of copy&pasting files when posting to the Dovecot mailing list. # '#' character and everything after it is treated as comments. Extra spaces # and tabs are