Permissions on shared folders

Hi,

I am having an annoying issue with kolab 2.1. I created
shared folders for 
teaching the spam filter as explained in the wiki. All my
users can access 
shared.spam and shared.ham just fine.

Now I want to restrict write access to the folders to
certain trusted users 
and only grant read access to anyone. I can do this via
kontact and the 
access rights are propagated just fine. However on the next
morning the 
access rights are gone and anyone has full access to the
shared folders 
again.

Anyone else experienced this? Any idea where to look? I
suspect a 
misconfiguration on my part but I don't know how to track
down the cause of 
this issue.

regards,
Andreas Micklei

-- 
Andreas Micklei
IVISTAR Kommunikationssysteme AG
Ehrenbergstr. 19 / 10245 Berlin, Germany
http://www.ivistar.de

Handelsregister: Berlin Charlottenburg HRB 75173
Umsatzsteuer-ID: DE207795030
Vorstand: Dr.-Ing. Dirk Elias
Aufsichtsrat: Dr. Jörg Gehler

_______________________________________________
Kolab-users mailing list
Kolab-userskolab.org
https:
//kolab.org/mailman/listinfo/kolab-users

Andreas Micklei <andreas.mickleiivistar.de> writes:

> Hi,
>
> I am having an annoying issue with kolab 2.1. I created
shared folders for 
> teaching the spam filter as explained in the wiki. All
my users can access 
> shared.spam and shared.ham just fine.
>
> Now I want to restrict write access to the folders to
certain trusted users 
> and only grant read access to anyone. I can do this via
kontact and the 
> access rights are propagated just fine. However on the
next morning the 
> access rights are gone and anyone has full access to
the shared folders 
> again.
>
> Anyone else experienced this? Any idea where to look?

If the settings get changed every night I assume there is
some kind of
cron job running every night that leads to the effect you
are
seeing. Which cron job get run every night?

Cheers,

Gunnar

> I suspect a 
> misconfiguration on my part but I don't know how to
track down the cause of 
> this issue.
>
> regards,
> Andreas Micklei
>
> -- 
> Andreas Micklei
> IVISTAR Kommunikationssysteme AG
> Ehrenbergstr. 19 / 10245 Berlin, Germany
> http://www.ivistar.de
>
> Handelsregister: Berlin Charlottenburg HRB 75173
> Umsatzsteuer-ID: DE207795030
> Vorstand: Dr.-Ing. Dirk Elias
> Aufsichtsrat: Dr. Jörg Gehler
>
> _______________________________________________
> Kolab-users mailing list
> Kolab-userskolab.org
> https:
//kolab.org/mailman/listinfo/kolab-users

-- 
______ http://kdab.com
_______________ http://kolab-konsortium.c
om _

prdus Kolab work is funded in part by KDAB and the
Kolab Konsortium

____ http://www.pardus.de
_________________ http://gunnarwrobel.de _
E-mail : prdus.de                                 Dr. Gunnar
Wrobel
Tel.   : +49 40 432 72335                          
Bundesstrasse 29
Fax    : +49 40 432 70855                            D-20146
Hamburg
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
~~~~~~~~
   >> Mail at ease - Rent a kolab groupware server at
prdus <<                 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
~~~~~~~~

_______________________________________________
Kolab-users mailing list
Kolab-userskolab.org
https:
//kolab.org/mailman/listinfo/kolab-users

Am Mittwoch, 24. Oktober 2007 schrieb Gunnar Wrobel:
> Andreas Micklei <andreas.mickleiivistar.de> writes:
> > Hi,
> >
> > I am having an annoying issue with kolab 2.1. I
created shared folders
> > for teaching the spam filter as explained in the
wiki. All my users can
> > access shared.spam and shared.ham just fine.
> >
> > Now I want to restrict write access to the folders
to certain trusted
> > users and only grant read access to anyone. I can
do this via kontact and
> > the access rights are propagated just fine.
However on the next morning
> > the access rights are gone and anyone has full
access to the shared
> > folders again.
> >
> > Anyone else experienced this? Any idea where to
look?
>
> If the settings get changed every night I assume there
is some kind of
> cron job running every night that leads to the effect
you are
> seeing. Which cron job get run every night?

Every night kolab gets stopped and backupped, then started
again. I also run 
spamandclam.sh every night.

regards,
Andreas Micklei

-- 
Andreas Micklei
IVISTAR Kommunikationssysteme AG
Ehrenbergstr. 19 / 10245 Berlin, Germany
http://www.ivistar.de

Handelsregister: Berlin Charlottenburg HRB 75173
Umsatzsteuer-ID: DE207795030
Vorstand: Dr.-Ing. Dirk Elias
Aufsichtsrat: Dr. Jörg Gehler

_______________________________________________
Kolab-users mailing list
Kolab-userskolab.org
https:
//kolab.org/mailman/listinfo/kolab-users

Maybe kolabd restart is reseting the ACL.
in some condition kolabd can check and try to
"repair" every mailboxes.

Andreas can you just restart kolabd and see if the
permission have changed ?


On 10/24/07, Andreas Micklei <andreas.mickleiivistar.de> wrote:
> Am Mittwoch, 24. Oktober 2007 schrieb Gunnar Wrobel:
> > Andreas Micklei <andreas.mickleiivistar.de> writes:
> > > Hi,
> > >
> > > I am having an annoying issue with kolab 2.1.
I created shared folders
> > > for teaching the spam filter as explained in
the wiki. All my users can
> > > access shared.spam and shared.ham just fine.
> > >
> > > Now I want to restrict write access to the
folders to certain trusted
> > > users and only grant read access to anyone. I
can do this via kontact and
> > > the access rights are propagated just fine.
However on the next morning
> > > the access rights are gone and anyone has
full access to the shared
> > > folders again.
> > >
> > > Anyone else experienced this? Any idea where
to look?
> >
> > If the settings get changed every night I assume
there is some kind of
> > cron job running every night that leads to the
effect you are
> > seeing. Which cron job get run every night?
>
> Every night kolab gets stopped and backupped, then
started again. I also run
> spamandclam.sh every night.
>
> regards,
> Andreas Micklei
>
> --
> Andreas Micklei
> IVISTAR Kommunikationssysteme AG
> Ehrenbergstr. 19 / 10245 Berlin, Germany
> http://www.ivistar.de
>
> Handelsregister: Berlin Charlottenburg HRB 75173
> Umsatzsteuer-ID: DE207795030
> Vorstand: Dr.-Ing. Dirk Elias
> Aufsichtsrat: Dr. Jörg Gehler
>
> _______________________________________________
> Kolab-users mailing list
> Kolab-userskolab.org
> https:
//kolab.org/mailman/listinfo/kolab-users
>


-- 
Alain Spineux
aspineux gmail com
May the sources be with you

_______________________________________________
Kolab-users mailing list
Kolab-userskolab.org
https:
//kolab.org/mailman/listinfo/kolab-users

Am Mittwoch, 24. Oktober 2007 schrieb Alain Spineux:
> Maybe kolabd restart is reseting the ACL.
> in some condition kolabd can check and try to
"repair" every mailboxes.
>
> Andreas can you just restart kolabd and see if the
permission have changed
> ?

Thanks for the hint! Indeed the permissions are lost when
kolab is restarted. 
Any hint where to look now?

-- 
Andreas Micklei
IVISTAR Kommunikationssysteme AG
Ehrenbergstr. 19 / 10245 Berlin, Germany
http://www.ivistar.de

Handelsregister: Berlin Charlottenburg HRB 75173
Umsatzsteuer-ID: DE207795030
Vorstand: Dr.-Ing. Dirk Elias
Aufsichtsrat: Dr. Jörg Gehler

_______________________________________________
Kolab-users mailing list
Kolab-userskolab.org
https:
//kolab.org/mailman/listinfo/kolab-users

On 10/24/07, Andreas Micklei <andreas.mickleiivistar.de> wrote:
> Am Mittwoch, 24. Oktober 2007 schrieb Alain Spineux:
> > Maybe kolabd restart is reseting the ACL.
> > in some condition kolabd can check and try to
"repair" every mailboxes.
> >
> > Andreas can you just restart kolabd and see if the
permission have changed
> > ?
>
> Thanks for the hint! Indeed the permissions are lost
when kolab is restarted.
> Any hint where to look now?

Can you create a new shared folder and repeat the test on it
?

>
> --
> Andreas Micklei
> IVISTAR Kommunikationssysteme AG
> Ehrenbergstr. 19 / 10245 Berlin, Germany
> http://www.ivistar.de
>
> Handelsregister: Berlin Charlottenburg HRB 75173
> Umsatzsteuer-ID: DE207795030
> Vorstand: Dr.-Ing. Dirk Elias
> Aufsichtsrat: Dr. Jörg Gehler
>
> _______________________________________________
> Kolab-users mailing list
> Kolab-userskolab.org
> https:
//kolab.org/mailman/listinfo/kolab-users
>


-- 
Alain Spineux
aspineux gmail com
May the sources be with you

_______________________________________________
Kolab-users mailing list
Kolab-userskolab.org
https:
//kolab.org/mailman/listinfo/kolab-users

* Andreas Micklei <andreas.mickleiivistar.de> [20071024
17:06]:
> Am Mittwoch, 24. Oktober 2007 schrieb Alain Spineux:
> > Maybe kolabd restart is reseting the ACL.
> > in some condition kolabd can check and try to
"repair" every mailboxes.
> >
> > Andreas can you just restart kolabd and see if the
permission have changed
> 
> Thanks for the hint! Indeed the permissions are lost
when kolab is restarted. 
> Any hint where to look now?

I suggest using ham/spam/whatever subfolders of a group
account and
manage the permissions using an IMAP client or cyradm
yourself.

Regards,
Thomas

-- 
thomasintevation.de - http://intevation.de/~t
homas/ - OpenPGP key: 0x5816791A
Intevation GmbH, Osnabrueck - Register: Amtsgericht
Osnabrueck, HR B 18998
Geschaeftsfuehrer: Frank Koormann, Bernhard Reiter, Dr.
Jan-Oliver Wagner

_______________________________________________
Kolab-users mailing list
Kolab-userskolab.org
https:
//kolab.org/mailman/listinfo/kolab-users