similar to: Sharing all mailboxes and userdb LDAP attrs

Hello, I'm wanting to make a shared folder that anyone in a domain can get to, but not anyone in any other domain. Here's my dovecot shared namespace: namespace { type = shared separator = / prefix = shared/%%u/ location = maildir:%%h:INDEX=~/shared/%%u subscriptions = no list = yes } The dovecot-dict-sql.conf.ext file has: map { pattern =

Hi all, I'm trying to set up public mailboxes for a subset of my users. This is on dovecot 2.2.27. I've created a new public namespace, and the new mailboxes indeed show up for everyone. So far so good. Now I want to restrict access: these mailboxes shouldn't be visible at all except to a fixed list of users. This part I can't seem to get working. I've added acl data

Hello, Thank you for your response. In answer to your questions I made a file global-acls containing: # cat global-acls Public/general user=user1 at domain.com lrwstipekxa Public/TestFolder user=user1 at domain.com lrwstipekxa Public/general user=user1 at domain2.com lrwstipekxa Public/TestFolder user=user1 at domain2.com lrwstipekxa Here's the ls -la output: #ls -la

Hello, Thanks, yes the global-acls file is the one I'm refering to and I created it before all this started. Yes, the users can both login properly and can access there own inboxes. Thanks. Dave. On 4/26/20, Markus Winkler <ml at irmawi.de> wrote: > Hi Dave, > > thanks for the information. > > On 26.04.20 18:37, David Mehler wrote: >> In answer to your questions

I'm getting inconsistent behavior from my acl file. I have an acl vfile configured with this: > Jobs$* anyone lrwikst > $* user=bob.wooldridge at edm-inc.com lrwstipekxa > $* user=michael.user at edm-inc.com lrwstipekxa > Jobs$* user=bob.wooldridge at edm-inc.com lrwstipekxa > Jobs$* user=michael.user at edm-inc.com lrwstipekxa The Jobs folder is a public shared folder. I

Hi Dave, thanks for the information. On 26.04.20 18:37, David Mehler wrote: > In answer to your questions I made a file global-acls containing: It's the '/usr/local/etc/dovecot/global-acls', right? > # cat global-acls > Public/general user=user1 at domain.com lrwstipekxa > Public/TestFolder user=user1 at domain.com lrwstipekxa > > Public/general user=user1 at

We have a solution using Dovecot as a secondary mail archive. All mailboxes are populated/groomed by master account and the actual users have only read access. This is achieved by a simple ACL approach. dovecot.conf has protocol imap { mail_plugins = acl quota imap_quota zlib } plugin { acl = vfile:/etc/dovecot/acls:cache_secs=300 } /etc/dovecot/acls/.DEFAULT file is trivial: user=master

Hi all, Might anyone have any idea about this issue? I can run a cron job if needed but it seems like autoexpunge SHOULD be doing this automatically... Thanks! --- Amir > On Jul 24, 2019, at 10:18 PM, Amir Caspi <Cepheid at 3phase.com> wrote: > > Hi all, > > I set up dovecot a couple of months ago and am having trouble getting autoexpunge=30d to work on my Trash and

Hi there, I'm testing dovecot 2.0.13 on Debian squeeze (deb from http://xi.rename-it.nl/debian) with the following doveconf -n. -------- # 2.0.13 (1449a2e2c1f5): /etc/dovecot/dovecot.conf # OS: Linux 2.6.26-2-openvz-amd64 i686 Debian 6.0.2 first_valid_uid = 8 mail_debug = yes mail_location = maildir:~/Maildir mail_plugins = listescape mail_log notify acl namespace { inbox = yes location

Hi all, I set up dovecot a couple of months ago and am having trouble getting autoexpunge=30d to work on my Trash and Junk mailboxes. Not sure why not because I'm not getting error messages in my log. Running "doveadm search -u <user> mailbox Junk savedbefore 30d" shows me many messages (I've got messages back to mid-May, and a couple of other users have them back to

I'm trying to set up global ACLs. I have the following in the config file: > # acl > mail_plugins = acl > > protocol imap { > mail_plugins = $mail_plugins imap_acl > } > > plugin { > # Without global ACLs: > #acl = vfile > > # With global ACL files in /etc/dovecot/dovecot-acls file (v2.2.11+): > #acl = vfile:/etc/dovecot/dovecot-acl > acl

Hi! What am I doing wrong here? Mission: Delete old empty sub mailboxes in our Public mailspace acl-file contents: MailingLists user=dag lrwstipekxa MailingLists/* user=dag lrwstipekxa Didn't work from my mail client so tried: Command tried: % doveadm mailbox delete -s MailingLists/Glibc -u dag doveadm(dag): Error: Can't delete mailbox MailingLists/Glibc: Permission

I'm experimenting with the Virtual plugin to give users access to folders like "All Mail", "Recent" and so on, similar to Gmail. Something like this works properly: mail_location = maildir:~/ namespace { inbox = yes location = prefix = INBOX. separator = . type = private } namespace { prefix = INBOX.virtual. separator = . location =

Hello, We have upgraded from Dovecot 2.2.13 to 2.2.15 and we are using global ACL file. The content of the ACL file is as following: * owner r INBOX owner lrwstipekxa INBOX/* owner lrwstipekxa user owner rwstipekxa user/* owner rwstipekxa This worked fine but after update any user cannot see any folders from under the INBOX, also they cannot create any new folders. Error into the logs are

Hello! I have the autoexpunge settings defined inside protocol imap thus (and it works): protocol imap { ? mail_plugins = quota notify replication imap_quota imap_sieve ? namespace inbox { ??? location = ??? mailbox Ham { ????? autoexpunge = 365 days ??? } ??? mailbox Spam { ????? autoexpunge = 365 days ??? } ??? mailbox Trash { ????? autoexpunge = 180 days ??? } ??? prefix = ? }

I just added a new namespace-alias with alias_for. Apparently this causes all mailbox indexes to be resynced? Is this intentional and/or is there some way to avoid this? My NFS storage pretty much kills its elf when hundreds of thausands of users needs to resync indexes :) Thanks -- Tom

I noticed the addition of a new namespace configuration "alias_for". What pracical difference is adding this over and above making namespace aliases hidden and disabling list, as in older versions of dovecot configurations? Joseph Tam <jtam.home at gmail.com>

still the same? root at buserver:/etc/dovecot# doveadm user test2 at onnet.ch field valueuserdb lookup: user test2 at onnet.ch doesn't exist relevant config output from doveconf -n userdb { args = /etc/dovecot/dovecot-ldap.conf driver = ldap result_success = continue-ok } userdb { args = username_format=%Lu /etc/dovecot/share.passwd driver = passwd-file result_failure =

Okay, this seems to be due to the fact that the option ?use_globals_only" is supported only in v2.2.31+ We are on Debian jessie with dovecot v2.2.13 ? even an upgrade to current stable stretch won?t help (dovecot v2.2.27). So we will wait until the packages find their way into the repository. thanks anyway > On 7 Aug 2018, at 13:00, Simeon Ott <simeon.ott at onnet.ch> wrote: >

It seems after checking the code that global ACL file functionality was changed at 2.2.14 so that only 1 rule is used, not multiple rules. This is not documented or said anywhere into change logs. Br, Ova -----Original Message----- From: dovecot [mailto:dovecot-bounces at dovecot.org] On Behalf Of Ovidiu Moldovan Sent: 10. helmikuuta 2015 10:26 To: dovecot at dovecot.org Subject: Dovecot 2.2.15