similar to: ACL and virtual user

Hi friends, I would like to remove write rights for a specific virtual user/email address. I've read the wiki "https://wiki2.dovecot.org/ACL" but there is nothing about it. So I started reading and rereading some old ML, like this: https://www.dovecot.org/list/dovecot/2006-June/013683.html where they talk about something like that but I would like to implement current

Steffen Kaiser ha scritto: > Does INBOX/Junk already exists? Yes, (but empty): find /var/vmail/hotelsangiorgioriccione.com/info/ |grep INBOX /var/vmail/hotelsangiorgioriccione.com/info/Maildir/.INBOX /var/vmail/hotelsangiorgioriccione.com/info/Maildir/.INBOX/Trash /var/vmail/hotelsangiorgioriccione.com/info/Maildir/.INBOX/Trash/new

On 06.10.2017 12:42:22, Aki Tuomi wrote: [..] >> >> Maybe it is not possible with Dovecot? >> >> Many Thanks >> >> Davide > > Just give the relevant permissions to the user, and it also requires > that the target directory is writable by source user. > > Aki Oh, excuse me for the (most probably) silly question, but where I could give to my

> On October 6, 2017 at 11:44 PM Davide Marchi <danjde at msw.it> wrote: > > > On 06.10.2017 12:42:22, Aki Tuomi wrote: > [..] > >> > >> Maybe it is not possible with Dovecot? > >> > >> Many Thanks > >> > >> Davide > > > > Just give the relevant permissions to the user, and it also requires > > that

I'm trying to set up a public namespace so that a set of IMAP folders are available to all staff - similar to MS Exchange Public Folders. I've managed to set up the namespace correctly but I'm having trouble with the ACLs. The global ACL file is the only method I can get to work. All I want to do is to allow 1 user admin privileges to create & delete anything but all other users

"Davide Marchi" <danjde at msw.it> writes: >> UW-IMAP's mailutil, imapsync, YippieMove and Larch. Whatever you use, *don't* use UW-IMAP's mailutil unless you got lots of time to kill. It is dreadfully slow -- I used it to export some of my users' mailboxes to Gmail or other remote mail servers, and I could almost cut&paste the messages faster. Like Aki

Global ACLs are intended to apply to a few mailboxes for all users. For example you could have a master user called "spam" that would have access to each user's "spam" mailbox, but nothing else. Global ACLs are kind of ugly. A mailbox's ACL is found from exactly the same name as what the mailbox's virtual name is. So for example if you have namespace { separator

> On October 7, 2017 at 1:29 AM Aki Tuomi <aki.tuomi at dovecot.fi> wrote: > > > > > On October 6, 2017 at 11:44 PM Davide Marchi <danjde at msw.it> wrote: > > > > > > On 06.10.2017 12:42:22, Aki Tuomi wrote: > > [..] > > >> > > >> Maybe it is not possible with Dovecot? > > >> > > >> Many

Il 2017-12-05 07:16 Sami Ketola ha scritto: [..] > > Trust us. We have run multiple migrations at scale of 10+ million > users. > > Sami However, it seems that Imapsync has license issues and in fact it's not included in the Debian repositories. Is it to be used anyway or should be avoid? Many thanks again Davide

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

> From: Thomas Leuxner <tlx at leuxner.net> >> cat /etc/dovecot/dovecot-acl >> * user=booking at hotelsangiorgioriccione.com lrwsi >> * user=info at hotelsangiorgioriccione.com lrwsi > Hi Davide, > > For LMTP to file the mails you need to add the p flag (POST). Well, I've added the "p" flag and now I will monitor the situation ;-) PS Just as an

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

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

hi! i'm davide from italy and i'm building one live version of Fedora Core3 and, would like to add the verbose bootsplash (for all strartup process) for it i doesn,t understand if is it depending from isolinux, or if i need a patched isolinux version many thanks! -- cosmogonia <http://www.cosmogonia.org/> noprovarenofareononfarenonc'?provare

Sami Ketola wrote:> We run all our migrations using Dovecot internal dsync. Usually using imapc connector to connect to legacy > platform. > > Wqmi Many thanks Wqmi! Well, I've read the dsync documentation, but this warning has me a little worried: "Make sure destination is exactly as source, deleting/reverting any changes in destination if necessary" So I followed

After updating from 2.2.22 to 2.2.33 rsp 2.3.8 my ACLs went bust. Below line in the global acl file hides all folders except INBOX for all users > * group=ALL Next reenable certain folders, eg: > Sent group=ALL lrwsi This made anyone see "Sent" in 2.2.22, but no longer so in 2.2.33 Any ideas how to have it like before? -- peter

Hi Friends, I would like to ask you a suggestion: I need to migrate a imap server to a new one and then dismiss the old one. Reading from relative Dovecot documentation page (https://wiki.dovecot.org/Migration), more tools are shown: UW-IMAP's mailutil, imapsync, YippieMove and Larch. The each mail servers are Linux based, one of this (mine) is Dovecot. Based on your experience which of

> On 3 Dec 2017, at 23.23, Davide Marchi <danjde at msw.it> wrote: > > Hi Friends, > I would like to ask you a suggestion: > I need to migrate a imap server to a new one and then dismiss the old one. > Reading from relative Dovecot documentation page (https://wiki.dovecot.org/Migration), more tools are shown: > > UW-IMAP's mailutil, imapsync, YippieMove and

On Mon, 4 Dec 2017 12:53:15 -0800 (PST) Joseph Tam <jtam.home at gmail.com> wrote: > "Davide Marchi" <danjde at msw.it> writes: > > >> UW-IMAP's mailutil, imapsync, YippieMove and Larch. > > Whatever you use, *don't* use UW-IMAP's mailutil unless you got lots > of time to kill. It is dreadfully slow -- I used it to export some of >

> On 13 Dec 2017, at 18.27, Davide Marchi <danjde at msw.it> wrote: > > Sami Ketola wrote:> We run all our migrations using Dovecot internal dsync. Usually using imapc connector to connect to legacy >> platform. >> Wqmi > > Many thanks Wqmi! > Well, I've read the dsync documentation, but this warning has me a little worried: > > "Make sure