Le 07/02/2020 à 11:35:10+0100, Paolo Cravero a écrit
> Hello Albert.
>
> > I would like to known what kind of ACL you give on a shared mailbox. My
> > problem is :
> >
> > I have some users who are admin on the mailbox, it's needed because those
>
Hello Albert.
> I would like to known what kind of ACL you give on a shared mailbox. My
> problem is :
>
> I have some users who are admin on the mailbox, it's needed because those
> admin-user can create sub folder.
>
> But some user make mistake time to time
Hi everyone,
I would like to known what kind of ACL you give on a shared mailbox. My
problem is :
I have some users who are admin on the mailbox, it's needed because those
admin-user can create sub folder.
But some user make mistake time to time and move the mailbox under some
Hello,
uhm, just a trivial question about ACL management. When I delete or
rename a mailbox, does Cyrus IMAP provide a process to find out all
orphan permissions and delete them on all other mailboxes rights?
Maybe something like "expire" could be useful, or a process that d
hed.
Regards,
Anatoli
*From:* Ellie Timoney
*Sent:* Tuesday, May 15, 2018 00:46
*To:* Anatoli
*Cc:* Info-cyrus
*Subject:* Re: setting acl on autocreate folders
Something like: autocreate_acl(multiple
autocreate_acl entries could be specified)
That's roughly what I'd expect such
an as "admins: postman" but none of these worked for
> plus+addressing (P+A), so the *postman* user appears to be some
> hardcoded way of dealing with LMTP delivery and has nothing in common
> with the normal users and operations.>
> If my assumptions are correct, I gu
are correct, I guess what Chen (OP) was asking would
be useful, i.e. to be able to define "anyone p" (either as a toggle
aimed at P+A or as a free-form for any user/ACL) for some auto-created
folders along the other auto-configuration features (autocreate_XXX,
x-list, etc.). The
So what I'm observing in practice is that the "-a" option is not enough
to deliver plus+addressed mails without the "anyone p" ACL permission in
the folder, which makes me think that the user for "-a" option is not
from the admins group, though it probably sho
(generally,
this means 'anyone' must have the 'p' right), otherwise the message
will just be filed into the user's INBOX.*
So what I'm observing in practice is that the "-a" option is not enough
to deliver plus+addressed mails without the "anyone p&q
imap.org/imap/reference/manpages/systemcommands/lmtpd.html#cmdoption-lmtpd-a)
> .>
> Thanks,
> Anatoli
>
> *From:* Ellie Timoney
> *Sent:* Friday, May 11, 2018 00:46
> *To:* Info-cyrus
> *Subject:* Re: setting acl on autocreate folders
>
>
> Hi Chen,
>
>
LMTP AUTH."
(https://www.cyrusimap.org/imap/reference/manpages/systemcommands/lmtpd.html#cmdoption-lmtpd-a).
Thanks,
Anatoli
*From:* Ellie Timoney
*Sent:* Friday, May 11, 2018 00:46
*To:* Info-cyrus
*Subject:* Re: setting acl on autocreate folders
Hi Chen,
So, the question : is it po
Hi Chen,
> So, the question : is it possible to set specific ACLs on autocreated
> folders ? (i.e., ACLs, different from those defined by defaultacl in
> imapd.conf).
I believe the autocreate mechanism has no particular knowledge of ACLs all all.
It just uses the standard Cyrus policy for assi
Hello,
This question has been asked twice before by different users, but no
answer has ever be given.
In 2012 : https://www.spinics.net/lists/info-cyrus/msg14612.html
In 2016 : https://www.spinics.net/lists/info-cyrus/msg17385.html
I guess the answer is NO, but just the same I thought i'd as
Hello,
I'm playing with autocreate mailboxes but I can't find a way to set
extraneous acl on the created mailboxes.
My users intensively use plussed addresses and they want those plussed
mail to be delivered in the correct folder.
This, to be achieved, needs the acl anyone:p be set on
"k" right on a nearest existing parent mailbox. When a
new mailbox is created, it SHOULD inherit the ACL from the parent
mailbox (if one exists) in the defined hierarchy.
"
V/r,
James Cassell
On Wed, Apr 13, 2016, at 10:06 PM, Bron Gondwana via Info-cyrus wrote:
> A
Ack. It still works like this
On Thu, Apr 14, 2016, at 03:51, Ken Murchison via Info-cyrus wrote:
> Unless someone other than me changed the code, ACL inheritance only
> applies to mailbox creation. Once a mailbox exists, its ACL is
> independent of all others.
>
>
> On 0
Ken Murchison via Info-cyrus wrote:
> Unless someone other than me changed the code, ACL inheritance only
> applies to mailbox creation. Once a mailbox exists, its ACL is
> independent of all others.
Thank you for your quick reply.
Cyrus Home Page: http://www.cyrusimap.org/
List
Unless someone other than me changed the code, ACL inheritance only
applies to mailbox creation. Once a mailbox exists, its ACL is
independent of all others.
On 04/13/2016 12:27 PM, Chris via Info-cyrus wrote:
All,
is ACL inheritance possible in shared namespace?
If I revoke access for
All,
is ACL inheritance possible in shared namespace?
If I revoke access for someone in folderA/, does this also apply to
folderA/subfolderA1?
Thank you in advance.
- Chris
Cyrus Home Page: http://www.cyrusimap.org/
List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/
To
On 2015-04-08 12:28, Luca Olivetti wrote:
> El 08/04/15 a les 10:11, Sven Schwedas ha escrit:
>
>>> Winbind uses a socket in /tmp/.winbindd but in the systemd unit file
>>> there's a
>>>
>>> PrivateTmp=true
>>>
>>> which effectively hides the socket from cyrus.
>>> Changing it to false solves the
El 08/04/15 a les 10:11, Sven Schwedas ha escrit:
>> Winbind uses a socket in /tmp/.winbindd but in the systemd unit file
>> there's a
>>
>> PrivateTmp=true
>>
>> which effectively hides the socket from cyrus.
>> Changing it to false solves the problem.
>
> I think it would be better to change th
On 2015-04-08 09:14, Luca Olivetti wrote:
> El 07/04/15 a les 18:10, Dan White ha escrit:
>> On 04/07/15 17:50 +0200, Luca Olivetti wrote:
>>> El 07/04/15 a les 17:31, Dan White ha escrit:
>>>
> localhost> sam m_sist group:m_sist lrw
> setaclmailbox: group:m_sist: lrw: Invalid identifier
>>
El 07/04/15 a les 18:10, Dan White ha escrit:
> On 04/07/15 17:50 +0200, Luca Olivetti wrote:
>> El 07/04/15 a les 17:31, Dan White ha escrit:
>>
localhost> sam m_sist group:m_sist lrw
setaclmailbox: group:m_sist: lrw: Invalid identifier
localhost>
>>>
>>> Could this be a permissions
On 04/07/15 17:50 +0200, Luca Olivetti wrote:
>El 07/04/15 a les 17:31, Dan White ha escrit:
>
>>> localhost> sam m_sist group:m_sist lrw
>>> setaclmailbox: group:m_sist: lrw: Invalid identifier
>>> localhost>
>>
>> Could this be a permissions problem? Can the cyrus user successfully
>> execute the
El 07/04/15 a les 17:31, Dan White ha escrit:
>> localhost> sam m_sist group:m_sist lrw
>> setaclmailbox: group:m_sist: lrw: Invalid identifier
>> localhost>
>
> Could this be a permissions problem? Can the cyrus user successfully
> execute the getent command?
Yes, it can
$ sudo su -s /bin/bash
On 04/07/15 16:28 +0200, Luca Olivetti wrote:
>I'm currently using cyrus-imapd 2.4.17 and sssd to obtain nss groups
>from an openldap server.
>I have some group acl which are currently working fine.
>I'm testing the migration to samba4 as an active directory domain
>con
El 07/04/15 a les 16:58, Sven Schwedas ha escrit:
>
> 1. Are you running cyrus on a Domain Controller, or on a normal member
> server?
member server
>
> 2. Which winbind/samba version(s) do you use?
3.6.25
>
> 3. smb.conf for the cyrus server?
[global]
security = ads
realm = SAMBA.WETRON.E
On 2015-04-07 16:28, Luca Olivetti wrote:
> I'm currently using cyrus-imapd 2.4.17 and sssd to obtain nss groups
> from an openldap server.
> I have some group acl which are currently working fine.
> I'm testing the migration to samba4 as an active directory domain
> con
I'm currently using cyrus-imapd 2.4.17 and sssd to obtain nss groups
from an openldap server.
I have some group acl which are currently working fine.
I'm testing the migration to samba4 as an active directory domain
controller and I'm trying to use winbind instead of sssd (which
Hi,
I'm experiencing some issues with Cyrus 2.4.17 and an add-on for
Thunderbird called "IMAP-Acl-Extension".
The ACL list window shows up empty and permissions can't be listed or
assigned.
This same add-on has worked when we were running Cyrus 2.3.
Does someone have a h
2 default. We started creating mailboxes in
Cyrus 2.2 and some mailboxes still have that ACL applied.
So I thought ... must be cases where the ACL stored in the cyrus.header
file diverges from the ACL stored in the mailboxes.db, but (used 'mbexamine'
on the production server to inspect the Cyrus
centOS-6.2
cyrus-imapd-2.3.16-6.el6_2.5
My question is: Is there a mechanism to automatically assign a
default acl to a specific mailbox upon creation? I found the
configuration option defaultacl but, this states that it is
specifically used by mailboxes OTHER than users.
The reason this
On Fri, 8 Apr 2011 20:35:53 +0200, Bron Gondwana wrote:
> On Fri, Apr 08, 2011 at 08:21:33PM +0200, Bron Gondwana wrote:
>> On Fri, Apr 08, 2011 at 06:17:37PM +0200, rosenber...@taoweb.at
>> wrote:
>> > But back to the question
>> > I read out the acl f
On Fri, Apr 08, 2011 at 08:21:33PM +0200, Bron Gondwana wrote:
> On Fri, Apr 08, 2011 at 06:17:37PM +0200, rosenber...@taoweb.at wrote:
> > But back to the question
> > I read out the acl from a mailbox
> > lrswipkxtecda
> > man cyradm
> > l = Look
> >
On Fri, Apr 08, 2011 at 06:17:37PM +0200, rosenber...@taoweb.at wrote:
> But back to the question
> I read out the acl from a mailbox
> lrswipkxtecda
> man cyradm
> l = Look
> r = Read
> s = Seen
> w = Write
> i = Insert
> p = Post
> k = Create
> x
Hello
i start writing a cyradm web frontend in php.
the old one php-cyradm was from the 2000 year and does not work on
newer php version.
But back to the question
I read out the acl from a mailbox
lrswipkxtecda
man cyradm
l = Look
r = Read
s = Seen
w = Write
i = Insert
p = Post
k
On Thu, Dec 09, 2010 at 03:27:59PM +0100, Sebastian Hagedorn wrote:
> Hi,
>
> no takers? I get that the developers are probably only concerned
> with 2.4.x, so perhaps one of you could try to verify if the
> behavior there is the same? Just try to set the ACL for a mailbox
> th
Hi,
no takers? I get that the developers are probably only concerned with
2.4.x, so perhaps one of you could try to verify if the behavior there is
the same? Just try to set the ACL for a mailbox that belongs to user using
the same account. If you try to set it to "weraslpki", does
Hi,
we're running Cyrus IMAP 2.3.14. We use a web frontend for ACL management
(originally written by Shawn Sivy, but adapted to RFC 4314 by me). Recently
we found that users cannot remove the 'x' right from their mailboxes.
Initially I assumed a bug in the CGI, because it work
Hi,
I'm running a cyrus server and there seems to be an issue using shared
folders. Child folders created by members of the share do not inherit
permissions from the parent folder. For instance share.staff has a set
of permissions allowing all users to access the content of that folder,
but the ch
;t
>> expecting.
>>
>> When a folder is deleted, it is moved to the DELETED hierarchy. However,
>
>> the acl on the folder remains the same (full access for the original
>> user).
>>
>> When a user deletes a folder, they see the deleted folder in t
On Mon, 2010-06-14 at 17:56 -0700, Andrew Morgan wrote:
> I am using delete_mode:delayed, and I noticed something I wasn't
> expecting.
> When a folder is deleted, it is moved to the DELETED hierarchy. However,
> the acl on the folder remains the same (full access for the
I am using delete_mode:delayed, and I noticed something I wasn't
expecting.
When a folder is deleted, it is moved to the DELETED hierarchy. However,
the acl on the folder remains the same (full access for the original
user).
When a user deletes a folder, they see the deleted folder in
Hello,
a listaclmailbox lists a very strange set of ACLs on a mailbox:
( - are valid users)
lrscd
fk
{16} "Strange, accented characters like `A" rswipcda
lrscd
a deleteaclmailbox "{16}*" fails, as does a
dam
My question is, how to remove all ACLs from this mailbox and set them to
a mor
On 25/11/09 12:43 +0100, Nicolas Chauvet wrote:
>>> acl oneuser: [lrsid]
>>> setting acl INBOX oneuser lrsid
>>> Could not set acl: 12 NO Permission denied
>>
>> I'm not quite following the --folderrec INBOX.${u} --regextrans2
>> 's/(.*)/INBO
Le mardi 24 novembre 2009 à 16:49 -0600, Dan White a écrit :
> On 24/11/09 20:16 +0100, Nicolas Chauvet wrote:
> >I'm trying to use imapsync between two cyrus-imapd servers.
> >At this time, synchronization of user mailbox went fine, with both
> >content and ACL
On 24/11/09 20:16 +0100, Nicolas Chauvet wrote:
>I'm trying to use imapsync between two cyrus-imapd servers.
>At this time, synchronization of user mailbox went fine, with both
>content and ACL. (using the cyrus account).
>
>But when I'm trying to use imapsync to s
Hello,
I'm trying to use imapsync between two cyrus-imapd servers.
At this time, synchronization of user mailbox went fine, with both
content and ACL. (using the cyrus account).
But when I'm trying to use imapsync to synchronize ACL for shared
maiboxes, I obtain this error:
acl oneus
Dan White wrote:
> On 21/10/09 18:05 +0200, Dietmar Rieder wrote:
>>> Dietmar,
>>>
>>> See RFC 4314 for an explanation of the acl flags.
>>>
>>
>> Dan,
>>
>> thanks for your hint. I did that already but (maybe I'm to stupid)
On 21/10/09 18:05 +0200, Dietmar Rieder wrote:
>> Dietmar,
>>
>> See RFC 4314 for an explanation of the acl flags.
>>
>
> Dan,
>
> thanks for your hint. I did that already but (maybe I'm to stupid) I
> couldn't figure out a set of flags,
Dan White wrote:
> On 21/10/09 17:54 +0200, Dietmar Rieder wrote:
>> Hi,
>>
>> is there a possibility to set an acl to a folder outside the users
>> INBOX hierarchy such as a user can not delete it but at the same time
>> it should be possible for her/him t
On 21/10/09 17:54 +0200, Dietmar Rieder wrote:
>Hi,
>
>is there a possibility to set an acl to a folder outside the users INBOX
>hierarchy such as a user can not delete it but at the same time it
>should be possible for her/him to create and delete subfolders in that
>fold
Hi,
is there a possibility to set an acl to a folder outside the users INBOX
hierarchy such as a user can not delete it but at the same time it
should be possible for her/him to create and delete subfolders in that
folder.
e.g.
The users INBOX is : user.testuser
The folder outside is
On Fri, 27 Feb 2009, Torsten Schlabach wrote:
> No, I wouldn't do that. But I might have restored mailboxes from server
> A onto server B. In that case I would assume that I can rely on UniqueId
> to be random enought to make a conflict *very* unlikely, can't I?
>
> BTW: I think, a reason why peop
Hi!
> but then our "FixUser" tool resets the ACLs just after
> reconstructing the mailboxes anyway
Where's that? I am not aware of this utility. What does it do? Just give
the mailbox owner the default ACLs back?
> hand copy a cyrus.header from the wrong directory in (in which case
> the Un
On Fri, Feb 27, 2009 at 12:18:00PM +0100, Torsten Schlabach wrote:
> Hi!
>
> >> I can imagine situations where this is not what you want.
> >
> > I can't. Please share a couple.
>
> If they are currupted for whatever reason?
50/50 chance that one or the other is corrupted, of course. Assum
Hi!
>> I can imagine situations where this is not what you want.
>
> I can't. Please share a couple.
If they are currupted for whatever reason?
I mean, by the books, reconstruct is a utility which you should not
need, because if nothing ever goes wrong, you will never have a need to
recons
On 26 Feb 2009, at 11:35, Torsten Schlabach wrote:
> I can imagine situations where this is not what you want.
I can't. Please share a couple.
:wes
Cyrus Home Page: http://cyrusimap.web.cmu.edu/
Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki
List Archives/Info: http://asg.web.cmu.edu/cy
On Thu, Feb 26, 2009 at 05:35:49PM +0100, Torsten Schlabach wrote:
> Dear list!
>
> Just a question:
>
> Cyrus keeps a backup copy of the ACL for each mail folder in the
> cyrus.header file.
>
> When doing a reconstruct -r -f, the ACL from the cyrus.header file is
>
Dear list!
Just a question:
Cyrus keeps a backup copy of the ACL for each mail folder in the
cyrus.header file.
When doing a reconstruct -r -f, the ACL from the cyrus.header file is
taken over and copied over to the mailboxes.db.
I can imagine situations where this is not what you want
Marc Patermann wrote:
> Hi,
>
> IMAPd 2.2.12 is connected with sasl ldapdb (ptloader) to an OpenLDAP
> (2.3.x) server.
>
> I can set acls with existing groups. I cannot set acls with non existing
> groups. So far: IMAPd is checking for groups in LDAP just right.
Afair, ldap group fixed in 2.3
Hi,
IMAPd 2.2.12 is connected with sasl ldapdb (ptloader) to an OpenLDAP
(2.3.x) server.
I can set acls with existing groups. I cannot set acls with non existing
groups. So far: IMAPd is checking for groups in LDAP just right.
localhost.ofd-h.de> sam user.foo.Junk group:bar read
localhost.ofd
t; to do this. Is it possible?
>> What version of Cyrus? If you're using 2.3.x, removing the 'x' right
>> from your users will prevent them from deleting the mailbox. I'd have
>> to check the ACL RFC, but I believe it will also prevent renaming (I
&g
using 2.3.x, removing the 'x' right
> from your users will prevent them from deleting the mailbox. I'd have
> to check the ACL RFC, but I believe it will also prevent renaming (I
> think RENAME need delete on the source and create on the destination).
> 2.3.7.
In
ared folder.
>
> I read through the cyradm documentation, but it wasn't very clear on how
> to do this. Is it possible?
What version of Cyrus? If you're using 2.3.x, removing the 'x' right
from your users will prevent them from deleting the mailbox. I'd have
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
I got a shared folder where I want users to be able to create
subfolders, but where I want to restrict the users so they do not move
or delete the shared folder. The folder is a top level shared folder.
I read through the cyradm documentation, bu
Hello,
i have the same trouble with group-acl on cyrus mailboxes with ldap
authentication. Do you have solved this problem?
Torsten Zumpf
> Hi List,
>
> I have some troubles with cyrus-imapd 2.2.12 on a i386 FreeBSD server.
>
> When trying to allow Fullcontrol to a mailbox l
Yes. The 'c' right controls CREATE/DELETE of mailboxes and the 'd'
right controls delete of messages. So, in your case, remove the 'c' right.
Lars Schimmer wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Hi!
>
> I setup a cyrus 2.1.18 on debian sarge.
> I tried to use a public I
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi!
I setup a cyrus 2.1.18 on debian sarge.
I tried to use a public IMAP folder and it works more or less fine.
One problem is annoying:
is it possible to set ACLs for the users to delete messages IN the
public folder but NOT delete the public folder
Hi!
- imapd 2.2.12 -
If I create a user's mailbox in cyradm,
# cm user.bla
in some cases the acl is set to
# lam user.bla
bla lrswipcda
and in some other cases there is no acl set.
# cm user.bla1
# lam user.bla1
{nothing}
All our users are in LDAP with ptsloader and sasl ldapdb.
IMAPd c
On Tue, Apr 24, 2007 at 02:25:21PM +0530, JOYDEEP wrote:
> thanks for your help. Yes u are right, now mail boxes are created with
> proper user permission.
> but I like to inform that I use felamimail with both
> cyrus-imapd-2.2.12-27.6 and cyrus-imapd-2.2.12-5
>
> now felamimail creates mail box
Janne Peltonen wrote:
> On Tue, Apr 24, 2007 at 12:24:32PM +0530, JOYDEEP wrote:
>
>> Same effect Janne :-( with unixhierarchysep: no mail boxes are
>> still created as user.
>> and this time even I can't manually create user/by cyradm
>>
>
> Yes, but wasn't your original probl
On Tue, Apr 24, 2007 at 12:24:32PM +0530, JOYDEEP wrote:
> Same effect Janne :-( with unixhierarchysep: no mail boxes are
> still created as user.
> and this time even I can't manually create user/by cyradm
Yes, but wasn't your original problem the permissions? Now, Cyrus
knows that u
Janne Peltonen wrote:
> On Tue, Apr 24, 2007 at 09:47:06AM +0530, JOYDEEP wrote:
>
>>> (you have unixhiersep enabled which makes . just another character in
>>> the mailbox name)
>>>
>> Thanks for the clarification. So what configuration changes should I
>> make in /etc/imapd.conf ?
>>
On Tue, Apr 24, 2007 at 09:47:06AM +0530, JOYDEEP wrote:
> > (you have unixhiersep enabled which makes . just another character in
> > the mailbox name)
> Thanks for the clarification. So what configuration changes should I
> make in /etc/imapd.conf ?
Change the line
unixhierarchysep: yes
to
u
Jo Rhett wrote:
> JOYDEEP wrote:
>> 1> if I create a mailbox like user/ it has the proper ACL
>> right. like
>> localhost> cm user/po
>> localhost> lam user/po
>> po lrswipcda
>>
>> 2> but if I create it like user. it has improper ACL ac
JOYDEEP wrote:
1> if I create a mailbox like user/ it has the proper ACL
right. like
localhost> cm user/po
localhost> lam user/po
po lrswipcda
2> but if I create it like user. it has improper ACL access
right. like
localhost> cm user.po
localhost> lam user.po
anyone lrs
Ye
JOYDEEP wrote:
Well I have found the problem.
1> if I create a mailbox like user/ it has the proper ACL
right. like
localhost> cm user/po
localhost> lam user/po
po lrswipcda
2> but if I create it like user. it has improper ACL access
right. like
localhost> cm user.po
localho
Dear list,
I am facing a typical problem here with cyrus-imapd-2.2.12-5.
the mail box created by felamimail email interface is automatically have
the "anyone" ACL right
for an example here is the lam command on an mailbox
-
localhost> lam user.t
Hi,
You dont have a "move" in imap. Only copy and delete.
Regards,
Olaf
On Wed, 2007-04-18 at 10:30 +0200, Heinz Ulrich Stille wrote:
> Hi!
>
> I've got one folder with many subfolders for archiving mail, and one special
> account which has access to these. So far t
Hi!
I've got one folder with many subfolders for archiving mail, and one special
account which has access to these. So far the acl allows inserting new
messages, but no deleting ("lrsipc").
Now I'd like to also allow moving messages around between subfolders (or
even to t
On 02 Aug 2006, at 21:03, Wesley Craig wrote:
It also includes: ... a reduction in the unnecessarily large amount
of memory that sync_server allocates for per-message pathnames;
I didn't make clear what the memory issue above is. For very large
mailboxes (>150K messages), the unnecessarily
Excellent. Looks good. I'll try it out soon.
In the meantime, I have encountered another ACL issue, and I'd like
to propose a solution.
Because 2.3.x currently stores ACLs in non-legacy format, when these
non-legacy ACLs are stored in a 2.2.x MUPDATE server, 2.2.x frontends
r
ather than paying
attention to whether the target backend supports only legacy ACLs).
Wes,
I just tested and committed a fix for the XFER 2.3 -> 2,2 ACL issue.
--
Kenneth Murchison
Systems Programmer
Project Cyrus Developer/Maintainer
Carnegie Mellon University
Cyrus Home Page: http://as
On Sat, 2006-07-15 at 02:32 +0200, Kellermann, Jan wrote:
> Hi,
>
> is there any solution to admin the Mailbox ACL´s over a Webinterface?
>
> It´s a lot of work to do this manualy by comandline for a lot of
> users.
>
> Or is there a way that i didn´t know?
>
&
Hi,
is there any
solution to admin the Mailbox ACL´s over a Webinterface?
It´s a lot of work
to do this manualy by comandline for a lot of users.
Or is there a way
that i didn´t know?
I want to have some
shared folders. To do this, i have a user "shared" with the subfo
Hello everyone. This is my first post in this list.
I am running Debian Sid with Cyrus IMAP 2.2.13. Previously I was using
Debian Sarge with Cyrus IMAP 2.1 and I was using UNIX groups to set up
ACL in the form of:
cyradm> sam user.customers group:reservations lrs
Time ago I was told that it
Hello everyone. This is my first post in this list.
I am running Debian Sid with Cyrus IMAP 2.2.13. Previously I was using
Debian Sarge with Cyrus IMAP 2.1 and I was using UNIX groups to set up
ACL in the form of:
cyradm> sam user.customers group:reservations lrs
Time ago I was told that it
IL PROTECTED]
Envoyé : vendredi 2 juin 2006 16:54
À : Brasseur Valéry
Cc : info-cyrus@lists.andrew.cmu.edu
Objet : Re: cyrus ACL and groups ...
Are your users stored in a LDAP server as well?
If so, then you can have Cyrus speak LDAP and get the info. Plus it
can do caching (ptscache_timeout)
In Cyrus
That nearly what i am looking for !!!
Where is the doc for pts ? and the LDAP part ?
Thanks
-Message d'origine-
De : Patrick Radtke [mailto:[EMAIL PROTECTED]
Envoyé : vendredi 2 juin 2006 16:54
À : Brasseur Valéry
Cc : info-cyrus@lists.andrew.cmu.edu
Objet : Re: cyrus ACL and g
_sock: /var/cyrus/socket/ptsock
look for ldap_* options in `man imapd.conf`
-Patrick
On Jun 2, 2006, at 4:31 AM, Brasseur Valéry wrote:
I have seen in the code that when you want to use groups in ACL for
cyrus, the group is a UNIX one ... (calling setgrent, getpwnam ... )
Is there a a way to use
On Fri, Jun 02, 2006 at 03:42:14PM +0200, Simon Matter wrote:
> > On Fri, Jun 02, 2006 at 10:31:46AM +0200, Brasseur Valéry wrote:
> >> I have seen in the code that when you want to use groups in ACL for
> >> cyrus,
> >> the group is a UNIX one ... (calling setgren
> On Fri, Jun 02, 2006 at 10:31:46AM +0200, Brasseur Valéry wrote:
>> I have seen in the code that when you want to use groups in ACL for
>> cyrus,
>> the group is a UNIX one ... (calling setgrent, getpwnam ... )
>> Is there a a way to use LDAP groups instead ...
&g
On Fri, Jun 02, 2006 at 10:31:46AM +0200, Brasseur Valéry wrote:
> I have seen in the code that when you want to use groups in ACL for cyrus,
> the group is a UNIX one ... (calling setgrent, getpwnam ... )
> Is there a a way to use LDAP groups instead ...
If you use nss_ldap, then cyru
I have seen in the code that when you want to use groups in ACL for cyrus, the
group is a UNIX one ... (calling setgrent, getpwnam ... )
Is there a a way to use LDAP groups instead ...
Thanks
Valery
Cyrus Home Page: http://asg.web.cmu.edu/cyrus
Cyrus Wiki/FAQ: http
Robert Schmid wrote:
>Again, this is what I expect. BUT I DON'T see any indicator that B has
>access to A.
>
>But when I login as 'B' and do 'lam *' I get
>
>B/b1/b2 default B lrswipcda
>...
>A/m1/m2/m3 default A lrswipcda
>...
>
>
>It's clear that B has access to A but so far my efforts to
to
>> these other mailboxes?
>
> What are the permissions on the mailbox that appears under Other Users?
> Perhaps there is an ACL on a subfolder of that mailbox that is granting
> access? What does "sam user.foo" say for the user foo in this case?
OK, I fixed my access probl
On Feb 8, 2006, at 1:25 AM, Andrew Morgan wrote:
On Tue, 7 Feb 2006, Robert Schmid wrote:
On Tue, February 7, 2006 20:38, Andrew Morgan wrote:
Perhaps if I can get this login problem fixed...
If you can't login as the cyrus admin user, then I don't know if
you can fix this...
If you a
should I look to find out how this user is getting access to
these other mailboxes?
What are the permissions on the mailbox that appears under Other Users?
Perhaps there is an ACL on a subfolder of that mailbox that is granting
access? What does "sam user.foo" say for the user foo in th
es.db.
Where else should I look to find out how this user is getting access to
these other mailboxes?
What are the permissions on the mailbox that appears under Other Users?
Perhaps there is an ACL on a subfolder of that mailbox that is granting
access? What does "sam user.foo"
1 - 100 of 202 matches
Mail list logo
