I have re-tested with RC2 and dovecot no longer crashes so the ACL plug-in is looking good, as is, for Dovecot 1.0 stable.
However the following ACL usability problems still exist:
- dovecot-acl file within public namespace directory isn't found
- global ACLs (vfile) partially work with virtual users but when used: a) non-ACL restricted public namespace directories stop working b) permitted users are unable to view or create sub-folders
Hopefully Timo has time to look at these problems after the 1.0 stable release because it would really help us here and I'm sure others would love to see access controlled Public Shared Folders.
As I am not a programmer I am unable to help coding wise but as we have a couple of clients requiring access controlled Public Shared Folders sponsoring the fix/development is not out of the question.
Testing Results:
VFILE TESTING:
owner lrwstiekxa user=virtualuser1@domain.com lrwstiekxa
Problems 2 (a) and (b) still exist. Sub-folder *is* created but not accessible
owner user=virtualuser1@domain.com lrwstiekxa
Problems 2 (a) and (b) still exist. Sub-folder *is* created but not accessible
user=virtualuser1@domain.com lrwstiek
Problems 2 (a) and (b) still exist. Sub-folder *is* created but not accessible
Regards, Gavin
On Sun, 2006-06-18 at 01:33 +0300, Timo Sirainen wrote:
On Thu, 2006-06-15 at 13:58 +1200, Fintec wrote:
I think all the above problems can be attributed to the fact the ACL plugin ignores the namespace prefix. I did further testing with the vfile using some suggestions from the list:
Could be, but supporting the namespace prefixes requires larger changes. Not going to happen before v1.0 release.
VFILE TESTING: ("vmail" is the local user)
Local user as in the UID of the process? That doesn't matter since only virtual users are matched.
owner lrwstiekxa user=vmail lrwstiekxa user=virtualuser1@domain.com lrwstiek
Dovecot Log: child 8872 (imap) killed with signal 11
It shouldn't be crashing. Could you get gdb backtrace of it? See http://dovecot.org/bugreport.html