Shared ROOM account

ladas

Hi everybody,
I created new shared user of room type. In accout settings I ticked:
Decline all meeting requests with scheduling conflicts and Accept conflict-free meeting requests.
When I sent new meeting request and include shared room account too, I should get meeting confirmation from room account and meeting should be added into its' calendar. BUT nothing happend. No confirmation is send back and no callendar record is created. Is it correct?
Another question: How can I add shared calendar of the room account at another user WEB GUI interface. At Outlook it works but at WEB GUI I did not find any way how to do that. WEB GUI Calendar documentation is empty, unfortunately.
Thank you very much for any answer.

rseiringer

Had same theme...

Got this from Support:

Haben Sie in in der /etc/gromox/exmdb_local.cfg auch die beiden Schalter an?

lda_twostep_ruleproc=1
lda_mrautoproc=yes

Unfortunately i couldn't test until now...

ozy

Could someone explain perhaps what lda_twostep_ruleproc=1 limitations are ?
From the Grommunio docs:

lda_twostep_ruleproc
If set to 1, an alternate rule processor codebase will be used which supports cross-store moves and OOF condition but (at this time) no delegation, or autoreply.
Default: 1

I can't wrap my head around this. OOF works but no autoreply ? Isn't OOF an autoreply ?

Btw, with lda_twostep_ruleproc set to 1, OOF messages work. and MTA notifications too. So what's autoreply then ?

WalterH

ozy Isn't OOF an autoreply ?

it is handled different.

ozy lda_twostep_ruleproc=1

is the two step role processor to move items into the public store. Unfortunately development did not implement all rules in this rule processor like no delegation or autoreply and this is a real pain.

ali34

Had same theme...

ot
Haben Sie in in der /etc/gromox/exmdb_local.cfg auch die beiden Schalter an?

ladas

I tested settings again and here is the result:
with both lines active, shared mailbox add the date into Calendar when there is no collision with other appointment, but confirmation email is not delivered. When there is a collision with other appointment, declined message is delivered back and appointment is not created.

ladas

Next udate:
After adding the two lines above, email forwarding rules for the users stop to work. Tested on rule "forward copy all incomming emails to another email address outside the server" .