similar to: Dovecot 2.2.13+ and master user db

Hi, We are trying to implement a highly secure mail server with user authentication restricted to SSL certificates only (not using passwords at all). Still, user information is stored in a LDAP directory. In this configuration LDAP is used to check whether the user is registered (and probably supply quota and other info), and actual authentication is done by SSL layer. According to wiki, a

Dovecot version 2.1.7 Ubuntu 12.04.3 LTS Kernel 3.2.0-35-generic x86_64 I'm not sure exactly when this started occurring, but sporatically users report issues receiving email, having email saved to "Sent," etc. Looking in dovecot.log, I see the following errors: 2013-10-16 09:53:20 imap-login: Info: Login: user=<user1>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, mpid=27434,

Hello, I'm currently experimenting with the 2.1.x series and am facing a behavior I can't explain; I must be doing something wrong and probably miss the obvious... ;-) This is a very basic build on Mac OS X 10.8.2: ./configure --prefix=/_COD/dovecot-2.1.14 --sysconfdir=/_ETC --localstatedir=/_VAR --with-sqlite --with-ldap=yes (Yes, I know, a strange layout, yet very convenient for

Hi! On 10.04.2018 19:31, David Mehler wrote: > Hello, > > I've got a few misc issues that I'm trying to get a handle on. > > I'm having what is probably a simple error with last logins. It's not > working, unable to write values to the database. Here's the log lines: > > 2018-04-10 10:43:34 imap-login: Info: Login: user=<user at domain.com>, >

I found and tried this work around on the man page: https://www.unix.com/man-page/all/5/ngroups_max/ but I still get the same "Too many extra groups" error even when I start dovecot with the above program to limit the # of groups. I suspect that dovecot is adding a number of groups when it starts up. I've hacked a work around to get it working for me on my laptop: diff --git

Hello Aki, Thanks for your suggestion. I followed it and the wiki at: https://wiki.dovecot.org/Plugins/LastLogin Good news, I get a record in the users table, with the username that just logged in. This is good. Bad news is I got unexpected output from the last_login time stamp. Here's the table and the user: mysql> describe users;

Hello, I've got a few misc issues that I'm trying to get a handle on. I'm having what is probably a simple error with last logins. It's not working, unable to write values to the database. Here's the log lines: 2018-04-10 10:43:34 imap-login: Info: Login: user=<user at domain.com>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, mpid=75934, TLS,

Hi, We get user's quota limit from LDAP. ?It works fine when user has quota attribute in LDAP (this is when it's different from default quota). But when user doesn't have quota limit attribute Dovecot doesn't take default value defined in quota plugin and assign unlimit quota to user. Our configuration is similar to the example from wiki (

I found an error in my log today... Dec 17 12:03:30 bubba dovecot: imap(user1 at amfes.com)<23017><VzQFnjx9WNAKO2EC>: Error: fts_solr: received invalid uid '0' Dec 17 12:04:44 bubba dovecot: imap(user2 at amfes.com)<25004><FeHDSj19i2ysOCn7>: Fatal: master: service(imap): child 25004 killed with signal 11 (core dumps disabled -

Hello all. Ok im now trying to make per user quota via LDAP. In LDAP im have attr: mailQuotaSize=210 Default dovecot quota=201M I edit my static db to this(from wiki): userdb static { args = uid=1002 gid=1002 home=/var/spool/dovecot/domains/%d/%n mailQuotaSize=quota_rule=*:storage=%$M } But in logs I see this: Info: auth(default): master out: USER 5 sysadmin at domain.off uid=1002

Hi, Maybe I am missing something simple, but I can't get users authenticated using password lookups, as opposed to auth_bind. This is how the log looks like when using password lookup: dovecot: auth(default): new auth connection: pid=2449 dovecot: auth(default): client in:

Hi, I am having trouble with the quota plugin with deliver. In the auth logs, I see that dovecot is able to get the attribute value just fine: *** Sep 21 17:49:30 dawnone dovecot: auth(default): ldap(cot,127.0.0.1): result: uid(user)=cot uidNumber(userdb_uid)=1011 gidNumber(userdb_gid)=1011 homeDirectory(userdb_home)=/home/cot mailQuotaSize(userdb_quota_rule=*:bytes=%$)=*:bytes=1000000 *** But

I have problem with quota limit settings for "deliver" - global plugin settings overrides userdb quota setting !!! imap and pop3 works fine. Quota limit for user is set to "quota=maildir:ignore=Kosz:storage=512". And "maildirsize" file in user's mail_location contains "524288S" line - good. But when I set: ---------------- plugin { quota =

Helo all, I'm trying to use Dovecot v1.1.beta13 lda with ldap. I made a tons of change in configurations but still can't set quota from ldap. See below: Log: Jan 16 17:37:09 mailserver-03 dovecot: auth(default): userdb(teste at xxx.com.br,127.0.0.1): Invalid GID value '*:bytes=1033' dovecot-ldap.conf: user_attrs =

Setting logging to debug reveals something is happening but the actual scripts do not run i suppose. Aug 21 11:54:23 imap(himbeere)<31571><ndLQjp2Q2K1/AAAB>: Debug: Mailbox INBOX: Mailbox opened because: SELECT Aug 21 11:54:23 imap(himbeere)<31569><kqPPjp2Q1q1/AAAB>: Debug: imapsieve: mailbox INBOX.Spam: MOVE event Aug 21 11:54:23

On 2019-08-21 12:30, Thomas Stein via dovecot wrote: > Setting logging to debug reveals something is happening but the actual > scripts do not run i suppose. > > Aug 21 11:54:23 imap(himbeere)<31571><ndLQjp2Q2K1/AAAB>: Debug: > Mailbox INBOX: Mailbox opened because: SELECT > Aug 21 11:54:23 imap(himbeere)<31569><kqPPjp2Q1q1/AAAB>: Debug: > imapsieve:

Hi, I'm new in this List, but I have 6 years using Dovecot on my debian from etch,lenny and now squeeze Package: dovecot-imapd Version: 1:1.2.15-4 Tags: squeeze -- System Information: Debian Release: 6.0 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-amd64 (SMP w/24 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8

v2.1.2 added support for "session IDs", which is a 9 year unique identifier for that specific IMAP/POP3 connection. Initially I thought it would only be useful for tracking connections going through Dovecot proxies to backends (the session ID is forwarded), but then I thought it could be useful for everyone if auth process also logs the session ID. So I thought for v2.1.6 I'd change

Hi, I tried to setup a master auth authentication. I also use auth_pop3wrapper to authenticate from qmail-ldap. But I could not login with master user. Here is the config. auth_master_user_separator = * passdb { driver = passwd-file args = /usr/local/etc/dovecot/passwd.masterusers master = yes pass = yes } passdb { # Path for checkpassword binary driver = checkpassword

Hello, I'm trying to get Dovecot 2.31, pidgeonhole 0.51 going with imapsieve and rspamd. I'm getting the below in my errorlog: cat dovecot.log 2018-04-13 17:35:34 imap-login: Info: Login: user=<testuser at domain.com>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, mpid=57977, secured, session=<o4T2psFpje5/AAAB> 2018-04-13 17:35:34 imap(testuser at