Questions about different type of accounts

[Pieter Vanmeerbeek]

You say that a resource account gives the calendar user access.

However I've made a setup with Konsec clients and was trying to use a
resource account for a room. Upon adding this account to a meeting request
an automatic reply came which indicated acceptance. 

However adding a second appointment at the same time interval using also
this room was also accepted.

My settings in the Kolab admin tool were

Account type : resource
Inivation policy : 

Anyone --> reject if conflicts
....   -- > Always accept

(this second option is not clear to me , whats its purpose? )

>From this I would expect a decline of the second meeting. What did I do
wrong?

I created a new data file into the outlook client, and checked the access
rights for the calendar folder. And only the resource itself had access to
it. Something even stranger, the calendar was empty. This could be a Konsec
related problem, as directly accessing the resource account on disk shows
message files. These message files contain a section 

>>
This is a Kolab Groupware object. To view this object you will need a client
that understands the Kolab Groupware format. For a list of such clients
please visit http://www.kolab.org/kolab2-clients.html
--=_5bcejg577yio
Content-Type: application/x-vnd.kolab.event; name="kolab.event"
Content-Disposition: attachment; filename="kolab.event"
Content-Transfer-Encoding: 7bit
<<

And all other calendar objects created by the Konsec client also contains a
tnef section. It also contains an xml section. So I suppose the tnef part
isn't really needed.

Kind regards,
Pieter
Able

-----Original Message-----
From: kolab-users-bounces at kolab.org [mailto:kolab-users-bounces at kolab.org]
On Behalf Of Bernhard Reiter
Sent: donderdag 24 november 2005 11:59
To: kolab-users at kolab.org
Subject: Re: Questions about different type of accounts

Am Dienstag, 22. November 2005 19:14 schrieb bud.golf4:
> What is the different type of users,
>
> user account.
> internal user account.
        same as user, but having in the internal subtree thus normal ldap
      searches will not find it.
> group account.
> ressource account.
      Both are close to user, but they give the calendar user access
      so automatic invitation handling can be used for simple resource 
planning.


--
NEW: aXs GUARD hands-on Trainings v.7.0 
more info at http://www.axsguard.com/indextraining.htm

aXs GUARD has completed security and anti-virus checks on this e-mail
(http://www.axsguard.com)
---------------------------------------------------
Able NV: ond.nr 0457.938.087