similar to: Public folders, individual SEEN flags

Should users of a shared mailbox be able to see both their personal inbox and that of the shared mailbox? Thanks, Keith Begin forwarded message: Date: Wed, 29 Jul 2009 17:50:08 +0100 From: Keith Edmunds <kae at midnighthax.com> To: dovecot at dovecot.org Subject: [Dovecot] Shared mailboxes and INBOX I'm trying to implement a shared mailbox: in other words, we have a generic email

I'm trying to implement a shared mailbox: in other words, we have a generic email address ("security@") which we want a number of users to be able to monitor. The problem I have is that users can see folders under that shared mailbox but can't see the INBOX. All the users in question have their own INBOX in their private namespace, so does this raise a conflict with monitoring

Is is possible to have a puppetmaster that is a client of a different puppetmaster? We manage our customers'' server via puppet, but one customer has a puppetmaster server which looks after their internal systems. We''ve tried the following in /etc/puppet/puppet.conf ("customer" and "us" replacing the domain names) on their puppetmaster: [puppetmasterd]

We started using Dovecot replication between two nodes and noticed that our configured private flags (INDEXPVT) in public/shared mailboxes are not replicated. We are only replicating INBOX namespace, as we dont want to replicate content of shared mailboxes for every user again. Is there a way to replicate the INDEXPVT or is that not (yet) implemented? Dovecot versions: # 2.2.31 (65cde28):

We've just converted to LAYOUT=fs. Some users had subfolders under Inbox, and for those users some MUAs no longer show those folders. The directory structure is that the cur, tmp and new folders are in the 'location' directory, but the subfolders are in $location/INBOX/$foldername. I am suspicious of this: 12 list "" INBOX * LIST (\HasNoChildren) "/"

> b) go to https://https://dovecot.org/mailman/listinfo/dovecot and click > unsubscribe, don't change your delivery options to notmail. That's not at all clear (quite apart from the double protocol prefix). A lot of the potential audience of this list "know" how Mailman works, so why have you broken that knowledge by delivering to those who have disabled mail delivery?

> I am very sorry that I had to enable the delivery for people who had > intentionally disabled delivery, but I didn't want to spend days > figuring out the best possible way to fix the situation and in the end > it's not a horrible bother to disable yourself again I have disabled mail delivery in Mailman. I'm still receiving the list mails. --

# dovecot --version 1.2.1 I'm trying to configure ACLs for public folders. I have: -------------------------------------------------------------------------------- namespace public { separator = / prefix = shared2/ location = maildir:/home/pubfolders2:INDEX=~/Maildir/public2 subscriptions = no list = children } protocol imap { mail_plugins = acl } plugin { acl = vfile }

Does Dovecot support public folders? I thought it may do via namespaces, but having searched the Wiki and the documentation, I can't find how namespaces are defined. I've probably not looked in the right place - any pointers? Thanks, Keith

I am having a problem with accessing a Samba share from a Windows 7 system. I think I have the Samba system configured correctly because I can join the Domain. root at ubuntu-server:/home/daved/AddToDCScripts# net rpc join -U Administrator Enter Administrator's password: Joined domain DEMLAND. I can use the smbclient to access the domain controller without a problem: root at

Dear all, sorry to bother the list again, I have a small configuration issue again with public (shared) folders. These folders should have per-user Seen flags, so I configured: namespace { type = public separator = . prefix = public. location = maildir:/var/mail/public:INDEX=%u/public subscriptions = no list = children } But this only seems to work with my account (presumably as I

Hi, After many hours of searching (!) and lots of testing procmail scripts, I found the explanation I was looking for -- something you explained at http://www.dovecot.org/list/dovecot/2008-July/032551.html That explains it. Thing is, though, every time I've seen shared mailboxes -- really shared by multiple staff or not -- the preference is in fact for the shared behaviours to also

Hi, I'm trying to use dovecot for storing mailing lists and read-only access for users. The OS is Solaris, authentication for all readers of these lists are from Ldap through PAM, and one local user "listuser" will receive all mail and store them into it's folders (Maildirs). These maildirs are readable (read-only) for all others and they are shared by setting --- mail_location:

Same problem here. I clicked the unsubscribed button, but didnt receive the email. Regards Jan On 30. 11. 18 10:50, glide3 at gmail.com wrote: > Same problem here. > > https://dovecot.org/mailman/options/dovecot-news > > Sadly the remind password button / unsubscribe email button click and claim > to send me a email but they don't. > > Assume its due a high

(Running Dovecot 1.1.0) Is it possible to either - (a) Still have shared "\Seen" flags even while using the dovecot-shared file or (b) Indicate to Dovecot in some way other than the dovecot-shared file which permissions to use for any messages created? The problem is, in my shared folder (using symlinks) scenario I am using, I have to use the dovecot-shared file to make sure new

I have the following as part of a module: -------------------------------------------------------------------------------- # Ensure "lsb-release" installed package {"lsb-release": ensure => installed, } # Use our sources.list file { "/etc/apt/sources.list": owner => root, group => root, mode =>

Hi, I've just switched mail storage from maildir to mdbox and found it's very amazing. The only question I've is related to shared mailboxes. In the past I've had a few mailboxes that were shared between two users by just symlinking maildir. So everything was shared including flags and \Seen status. Now I want to get something like this. As far as I understand,

Hi all, I wanna to set up shared folders for a couple of users and I'd like that everyone could keep the \Seen flag as private. So if user #1 reads some messages and user #2 not, those messages appear as "unseen" to #2 and "seen" to #1. I've implemented shared folders using namespaces with every user having their own "control" and "private"

Well, the log shows that I'm getting an Access Denied on the SAMR_OPEN_DOMAIN rpc... does that point anyone to my problem? 2004/02/17 09:36:47, 3] rpc_server/srv_pipe.c:api_rpcTNP(1509) api_rpcTNP: rpc command: SAMR_OPEN_DOMAIN [2004/02/17 09:36:47, 3] lib/util_seaccess.c:se_access_check(251) [2004/02/17 09:36:47, 3] lib/util_seaccess.c:se_access_check(252) se_access_check: user sid is

We have a customer with a large public folder hierarchy. They occasionally make requests to have the public folder ACLs changed; for example: "please give user X access to all public folders" (that's nearly 1700 folders). Worse: "please give user Y access to all sales folders" (there are 1450 sales folders). The problem is that there are (naturally) spaces in the folder