<html><head></head><body><div style="font-family: Verdana;font-size: 12.0px;"><div>
<div>Hi Thomas,</div>
<div> </div>
<div>as far as I know "ACT_" is a legacy prefix.</div>
<div>You should use "ALL_" or "EVENT_ "or "TASK_" prefixed options.<br/>
We use "ALL_" in kolab.conf and have no problems. (Kolab 16 )</div>
<div> </div>
<div>CU,</div>
<div>zx10</div>
</div>
<div>
<div>
<div name="quote" style="margin:10px 5px 5px 10px; padding: 10px 0 10px 10px; border-left:2px solid #C3D9E5; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">
<div style="margin:0 0 10px 0;"><b>Gesendet:</b> Mittwoch, 09. September 2020 um 09:08 Uhr<br/>
<b>Von:</b> "Reitelbach, Thomas" <tr@erdfunkstelle.de><br/>
<b>An:</b> users@lists.kolab.org<br/>
<b>Betreff:</b> Re: Aw: Do not email attendees upon appointment updates</div>
<div name="quoted-content">Thank you for your reply,<br/>
<br/>
I will first test with the global option in kolab.conf and try<br/>
"ACT_SAVE_TO_FOLDER". I'm not sure if this is the right option for my<br/>
case, but let's see.<br/>
<br/>
I don't want _all_ itip messages to be omitted.<br/>
<br/>
But I stumble over a possible glitch in the documentation at<br/>
<a href="https://docs.kolab.org/administrator-guide/smtp-content-filtering.html#admin-wallace-invitation-policy" target="_blank">https://docs.kolab.org/administrator-guide/smtp-content-filtering.html#admin-wallace-invitation-policy</a><br/>
The possible documented options begin with "ALL_" but in the default<br/>
configuration in my kolab.conf there is this example:<br/>
<br/>
kolab_invitation_policy = ACT_ACCEPT_IF_NO_CONFLICT:example.org,<br/>
ACT_MANUAL<br/>
<br/>
--> "ACT_" instead of ALL_ --- is this a bug of the documentation or<br/>
does my default configuration have a bug or are both options valid?<br/>
ACT_ACCEPT and ALL_ACCEPT? I see there are more options like<br/>
EVENT_ACCEPT and TASK_ACCEPT.<br/>
<br/>
Cheers<br/>
Thomas<br/>
<br/>
Am 07.09.2020 21:33, schrieb zx10@gmx.net:<br/>
> Hi Thomas,<br/>
><br/>
> you can define certain settings for the organizer with "invitation<br/>
> handling policy" in WAP or define global options for the domains in<br/>
> kolab.conf.<br/>
> It is also possible to set the "kolabInvitationPolicy" attribute in<br/>
> LDAP.<br/>
> Maybe "ALL_Accept" is the right choice for this usecase.<br/>
><br/>
> See<br/>
> <a href="https://docs.kolab.org/administrator-guide/smtp-content-filtering.html#admin-wallace-invitation-policy" target="_blank">https://docs.kolab.org/administrator-guide/smtp-content-filtering.html#admin-wallace-invitation-policy</a><br/>
><br/>
><br/>
> hint: If you set the global option in kolab.conf, you will need to<br/>
> restart Wallace. Just said because I forgot this more than once ;-)<br/>
><br/>
> CU,<br/>
> zx10<br/>
><br/>
> Gesendet: Montag, 07. September 2020 um 15:37 Uhr<br/>
> Von: "Reitelbach, Thomas" <tr@erdfunkstelle.de><br/>
> An: users@lists.kolab.org<br/>
> Betreff: Do not email attendees upon appointment updates<br/>
> Hello list,<br/>
><br/>
> In our Kolab environment we mainly use one single big calendar which<br/>
> is<br/>
> shared with several users in the office.<br/>
> For our office this works quite well since several years.<br/>
> But everytime when someone makes a change to an appointment an update<br/>
> email is sent to the organizer (which in turn is a shared mailbox with<br/>
> several users, so many people get these update-emails). This is<br/>
> annoying<br/>
> and useless for us.<br/>
><br/>
> I know that in roundcube one can uncheck the corresponding option when<br/>
> he edits an appointment, so that the update email is omitted, but our<br/>
> users usually forget it almost everytime.<br/>
><br/>
> But I thought there might be a setting or a way to disable these<br/>
> „updated appointment" emails at all. Has someone a good idea where<br/>
> to<br/>
> look at? Maybe wallace? I'm a bit stuck here.<br/>
><br/>
> We're talking about Kolab 16.1.<br/>
><br/>
> Cheers<br/>
> Thomas<br/>
> _______________________________________________<br/>
> users mailing list<br/>
> users@lists.kolab.org<br/>
> <a href="https://lists.kolab.org/mailman/listinfo/users" target="_blank">https://lists.kolab.org/mailman/listinfo/users</a><br/>
> _______________________________________________<br/>
> users mailing list<br/>
> users@lists.kolab.org<br/>
> <a href="https://lists.kolab.org/mailman/listinfo/users" target="_blank">https://lists.kolab.org/mailman/listinfo/users</a><br/>
_______________________________________________<br/>
users mailing list<br/>
users@lists.kolab.org<br/>
<a href="https://lists.kolab.org/mailman/listinfo/users" target="_blank">https://lists.kolab.org/mailman/listinfo/users</a></div>
</div>
</div>
</div>
<div> </div>
<div class="signature"> </div></div></body></html>