|
I was misreading the RFC and I now
understand how one of my users was able to delete a few gigs of
email and folders: the folders had been migrated from a pre-2.3.0
message store and I hadn't retuned the permissions on those
folders. Having now retested on two 2.4 servers and a 2.5.4 I am
now content that this was a PEBSAK. Fortunately, I have a
backup...
Thanks for the help!
John
On 30/07/15 19:58, Dan White wrote:
I was
just looking through 2.5.3. See lib/acl.c, which looks reasonable
(for that version).
On 07/30/15 19:56 +0100, John wrote:
But I am
setting e and t and getting back e, t and d and it is behaving
like x is set. I think I might be taking a trip to the source
code again :(
John
On 30/07/15 19:44, Dan White wrote:
RFC 4314
was implemented in 2.3.0 (according to the changes file).
So with 'd' listed, e, t, and x are implied, per the RFC.
This is way out of date date unfortunately:
http://cyrusimap.org/docs/cyrus-imapd/2.5.4/overview.php
Check your 'defaultacl:' option to verify it doesn't contain
d.
On 07/30/15 19:09 +0100, John wrote:
I set
the ACL to lrswiptek and it then shows as lrswipktecd. Have
I
missed a database migration step at some point in the past?
The current
server is running 2.4.12 (and I have a project to move it
all to 2.5.x
soon).
John
On 30/07/15 16:37, Dan White wrote:
On
07/30/15 16:21 +0100, John wrote:
Hi
List,
I have a bunch of shared folders which I want to have
various user
permissions on them. I can do the simple read/write
ones, but I cannot
work out how to allow a user to delete mails but not the
mailbox. A
user
has just done it *again* so I need to get it sorted.
https://www.ietf.org/rfc/rfc4314.txt
You want 't' and not 'x'.
|
----
Cyrus Home Page: http://www.cyrusimap.org/
List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/
To Unsubscribe:
https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus
