similar to: shared folders

Hello, I'm running dovecot 2.1.9 and I'm trying to configure shared folders. So, as described at http://wiki2.dovecot.org/SharedMailboxes/Shared I have configured a namespace like this: namespace { type = shared separator = / prefix = shared/%%u/ location = maildir:%%h/Maildir:INDEX=~/Maildir/shared/%%u subscriptions = no list = yes } In one user (user1) I have configured ACLs

Hi, some change between ff5c341f8838 and f30437ed63dc seems to have broken auth: => Bad Login Mar 23 09:01:46 spectre dovecot: master: Dovecot v2.1.3 (f30437ed63dc) starting up [...] Mar 23 10:25:44 spectre dovecot: auth: Debug: auth client connected (pid=7266) Mar 23 10:25:45 spectre dovecot: auth: Debug: client in:

I have configured dovecot to have a shared namespace so users can share there inboxs with each other but no matter what paths i give it i cant see the folder in thunderbird I've checked my db is listing to and from i've checked i have correct permissions, i'm sure i have everything right here is my config and extract of the debug log while i use the list acl's and try and

Ah. You probably need to change ldap userdb so that you add userdb { driver = ldap ? args = /etc/dovecot/dovecot-ldap.conf result_success = continue-ok } so that the next one is processed. you can use 'doveadm user test at onnet.ch' to verify that the attributes are read for this user, and with another username that they are not. Aki On 07.08.2018 12:23, Simeon Ott wrote: > ?

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: >

I am using Dovecot in two Server environments. My Legacy (5 years+ old) servers are running dovecot 1.1.20, and are responding as expected. These servers are using an NFS based storage for the /home directory structure, and are working beautifully. However, I need to replace these inefficient servers, and get more current. That brings me to the problem, where I am implementing Dovecot

Hmm. if you put it *after* the ldap userdb, it should not have prevented users from logging in. What happens if you do userdb { ? driver = passwd-file ? args = .... ? skip = notfound ? result_failure = continue-ok } Aki On 07.08.2018 12:58, Simeon Ott wrote: > Now the attributes are correctly read for the user test at onnet.ch > <mailto:test at onnet.ch>, but other users are not

Hello, I'm trying to configure dovecot (2.0.13) to cache user and pass dbs. This a mail server whose purpose is only to deliver messages through dovecot lda. My users are in a ldap server. So I have configure auth_cache_size (with 20MB) and auth_cache_ttl (with 1 day). I have checked that caching is being done, and it is. If a send a message to a user, dovecot looks for it in my ldap

Hi all my Linux system: opensuse 11.2 my mail system: postfix - dovecot my key problem since several days googling and testing is: how can I have a pop account with dovecot for a user if that user is NO linux system user it appears to me that most auth mechanisms somehow expect a mail user also to be a linux system user either to be found in the /etc/passwd or /etc/alias on my 4 servers I

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:

Fix typo, you have schme. Aki On 07.03.2018 15:47, Sergio Belkin wrote: > 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:

Good day, everyone. I'm playing around with replication to create a backup host. I have hosts backend3 (192.168.100.112) and backend3-replica (192.168.100.113). backend3 acts as a mail-receiving host, backend3-replica is a backup for the case of failure. Both versions are 2.2.13 (form Debian Jessie repository). backend3 receives mail via LMTP-proxy. So far I've managed to setup

Hi, can anyone tell me where these "unknown users" come from. As far as I see the fact, dovecot is asked by postfix to look for the password of the recipient-user (why ever). +++ Jan 7 19:43:09 f42252se postfix/smtpd[14625]: initializing the server-side TLS engine Jan 7 19:43:09 f42252se postfix/tlsmgr[14627]: open smtpd TLS cache btree:/var/lib/postfix/smtpd_scache Jan 7 19:43:09

Hi, I configured shared mailboxes and get an error when i use SQL as the acl_shared_dict. It works when i use a file instead. With SQL as the shared_dict, dict crashes. I have enabled sql query logs on the mariadb server, the table user_shares and anyone_shares are queried but there is no insert to the empty tables. The dovecot-acl files are created in the mailbox when i add an acl with

I've been pouring over the documentation for dovecot, but can't find a solution to this problem. I recently took over administration of the dovecot email service at the University where I work, and things were going smoothly. We've been creating email accounts for use with JIRA, a bug reporting/tracking system, and one day recently, when I tried to add a new account to JIRA, I got

This is a tired old topic but I've at least got an angle on it: Outlook Express works perfectly with IMAP / SPA for users logged into our Windows domain; I just give the server address and username, and it logs in without any password required; beautiful! auth_ntlm_use_winbind = yes auth_winbind_helper_path = /usr/bin/ntlm_auth auth default { mechanisms = ntlm userdb static { args =

Hi! I install dovecot from debian-backports: dovecot --version 2.2.9 Dovecot is configured to multiple authorization: /etc/dovecot# cat conf.d/10-auth.conf |grep include #!include auth-deny.conf.ext !include auth-master.conf.ext #include auth-system.conf.ext !include auth-sql.conf.ext !include auth-ldap.conf.ext #!include auth-passwdfile.conf.ext #!include auth-checkpassword.conf.ext #!include

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

Now the attributes are correctly read for the user test at onnet.ch <mailto:test at onnet.ch>, but other users are not able to authenticate anymore. root at buserver:/var/spool/postfix/virtual/onnet.ch/test/Maildir/.super# doveadm user test at onnet.ch field value uid 5000 gid 5000 home /var/spool/postfix/virtual/onnet.ch/test/ mail maildir:~/Maildir quota_rule *:bytes=1073741824 acl

Dec 14 14:33:03 test2 dovecot: auth: Debug: auth client connected (pid=24143) Dec 14 14:33:14 test2 dovecot: auth: Debug: client in: AUTH#0111#011PLAIN#011service=pop3#011secured#011session=D6dl6dDQdAAAAAAAAAAAAAAAAAAAAAAB#011lip=::1#011rip=::1#011lport=110#011rport=38004#011resp=<hidden> Dec 14 14:33:14 test2 dovecot: auth: Debug: